yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Please check into the Troubleshooting guide - there are many more possible things how apps may detect root and how possibly to overcome than just hiding from Magisk (like hiding Magisk Manager, uninstalling suspect apps like Titanium, removing TWRP folder and so). You can also find about searching back, every week somebody asks again for the same thing

And please check your post and remove (two) duplicates
[Magisk] FailSafeNow:
I've got some problems. My Magisk modules aren't working. I'm using matteo's build of LineageOS 16 for milletwifi. I used to have the mods working, but not anymore. First I noticed my audio mods had stopped working. Then I noticed ACC had stopped working. And then it was Riru for XPosed.

I lost the functionality when I upgraded from the June build to the July. I simply installed over what I had. When I discovered the problem, I tried reinstalling the OS clean, but it still didn't work. I even tried a clean install of the June build, but it didn't fix things.

How do I troubleshoot this thing? It's annoying. I need my modules to work.
[Magisk] BeeJ1109:
Hi

My Milletwifi T330 works Stable no issues with latest LOS 16 08082020 with modules no issues.

Cheers
[Magisk] gvsukids:
I used the flash option to install the August security update. I then uploaded the boot.img from the downloaded August security update and patched it via magisk. Then I installed the patched_boot via CMD from the laptop, and upon rebooting the phone the screen unlock wouldn't respond to my input.
[Magisk] zgfg:
You didn't even mention your phone make and model?! Pls be aware that this is not a Pixel XYZ or something forum, it's a generic thread for Magisk with users ranging from Samsung, HTC, Huawei, One Plus, etc, you name it.

Hence for us who are not using the same phone as you, we don't know which firmware with Aug Sec. patch you talk about (update policies and methods, tricks, issues - they are all device specific, and only users from the same phone or at least same brand can help about)

In short, either be specific and give details hoping that there is here a user familiar with your device who can give you device-specific hints, or first of all check and ask on the XDA sub-forum for your particular device

It's in your interest, and the interest of your phone ?, to get the first-hand help from the experts who are familiar with the phone and firmware you (implicitly) thought about
[Magisk] gvsukids:
Pixel 3
[Magisk] FailSafeNow:
After I discovered that reverting to the older version didn't help me, I just said "screw it" and upgraded to August. But this version isn't working either. How can I fix it? I don't even know how to begin troubleshooting the problem. Can I get anyone a log?
[Magisk] BeeJ1109:
Hi FailSafeNow.

Suggest a clean flash first, then reinstall August version then root with Magisk using August boot.img to make modified.boot.img. Then flash via TWRP v3.4.0-4.

If that fails you need to start with Stock, flash using ODIN on PC, USB cable. Need Samsung Drivers. ODIN v3.14.4 and Stock ROM from Sammobile site. Install Magisk using stock boot.img extracted from download. Create magisk.boot.img to Root device. Then install TRWP. Once TAB is working. Use TWRP Nandroid backup. On ExtSDCard for later restore, if required.

Then Gapps micro or pico for ARM Android 9. previously downloaded and stored on ExtSDCard. Not internal memory as you may remove the file using Factory Reset Wipe.

Download and store ROM on ExtSDCard as well.

Then do a Clean wipe, using Factory reset in TWRP. Now you should be really to flash LOS 16 08082020.

Don't Reboot now, flash Gapps. Now Reboot. Re install Magisk, using boot.img extracted from LOS to create the correct modified magisk.boot.img. to correctly Root device with boot.img to match LOS 16 ROM.

Using Stock boot.img will fail if used with Newly installed ROM.

Check TWRP is working. Create Nandroid backup , store on ExtSDCard to restore if required later.

Now reboot into System and continue to install apps are required from your personal store or playstore.

Good to go. ALL Should work now. If still issues you can restore Stock or LOS. Try again.

Best of Luck

Cheers
[Magisk] pndwal:
- Magisk at 'feature freeze stage' for upcoming Stable build (slated for release pre Official Android 11).

- Custom module repo support coming sometime later.

- John cautions 'USING CUSTOM MAGISK MANAGER' forks with custom repo etc 'IS DANGEROUS!' as these get root access.

https://mobile.twitter.com/topjohnwu/with_replies PW
[Magisk] FailSafeNow:
Interesting the way you describe it. I always did a clean install by wiping System, Data, Cache, and Dalvik Cache, then flashing the ROM, then GAPPS, then Magisk, then rebooting. But you're talking about doing separate stuff with boot.img. Correct me if I'm wrong, but when I flash the ROM, doesn't that flash boot.img?

I suppose I could try a clean install all over again. I suppose. But... I clean-installed the June build and then installed my modules, and it still didn't work. Granted, I restored my apps first. What's messing things up? Is there a bad app interaction? Isn't there any way to work from where I am now, without having to reinstall everything all over again? Would a logcat help?
[Magisk] amk316:
thanks John Wu

Magisk Manager (65f88e4a) (294) fixed my banking apps

the only app lift is McDonald app!!!!!
[Magisk] thearmeddiyer:
So I started a thread in galaxy s10+ questions and answers but havent had any replies.

Here is my problem, first my phone is a samsung galaxy s10+ (sm-g975f/ds exynos) android version 10 with factory ROM. I have successfully installed Magisk 20.4 with magisk manager 7.51 and TWRP version 3.3.1.

I have discovered that wiping cache as well as entering safe mode effectively breaks the magisk installation. after both events the phone will boot into non-magisk mode and work fine (without root) but when booting into magisk mode I cant get past the lock screen. It will allow me to put in my pin and press ok and then it brings me right back to the lock screen. In an attempt to get past that I removed any type of lock screen at which point as soon as it hits the home screen in magisk mode it will reboot and keep rebooting until it finally decides to boot in non-magisk mode. I'm not sure if wiping cache or booting into safe mode is a known cause for breaking a magisk install but I can avoid doing those in the future.

My real problem is that the camera doesnt work at all. I can open the app but the physical camera does not turn on and will give me an error message saying the camera has failed. I have tested this with the factory samsung camera app as well as 2 other aftermarket/open source camera apps with the same result. Both times I broke the magisk install as stated above were attempts to get the camera working. Both times after breaking the install the camera would work in non-magisk mode. Also when booting into safe mode the camera also worked. So as it stands now I can either have root or a working camera on my phone but not both.

I will start fresh and try and not break the install again in figuring this problem out but I have got pretty quick on flashing firmware at this point haha. The only other ideas I have are using magiskhide or giving the camera app superuser rights, but if anyone else has ideas please let me know.

Thanks in advance for any help.
[Magisk] rash.m2k:
I have an issue with Magisk, I need to change the contents of /oem/OP/cust_path_mapping.cfg file on my LG G7 thinQ. So i've got root access and when I attempt to change the contents and reboot, there are no changes saved.

So I copied the hosts module folder under /data/adb/modules to create my own module. So I create a oem/OP/cust_path_mapping.cfg under the system folder and reboot and the folder oem under system is gone!!! WTF??????? Can someone tell me WTF is going on?
[Magisk] BeeJ1109:
Hi Yes if you are Flashing Stock or Custom boot.img will be restored without root.

I was adding that boot.img may need to be re-patched using Magisk. If you lost Root during re-flashing. Depends on your process.

My Galaxy Tab 4 milletwifi with LOS16 by Matteo August build. With Magisk 20.4 Rooted with TWRP v3.4.0-3. With 180 apps. Magiskhide & some modules All working no issues. I restored apps using either Google Cloud backup as well Titanium Backup APPs ONLY.

Limited issues, Suggest a Total Wipe, excluding ExtSD card & OTG (if using that for backup). Then Start Clean ROM , not Dirty Flash, then restore apps, even one at a time.

Very time consuming first time, but once working, Backup Apps to allow easy to Backup & Restore.

Cheers
[Magisk] Didgeridoohan:
I'm assuming that /oem is it's own partition and not just a symlink to a folder in /system.

Magisk does not allow creating new directories and files directly in the root of /system, so if there is no /system/oem originally it will be removed from the module.

This is a safety feature, since many devices will have issues when a Magisk module creates new directories or files in the root of the system partitions.
[Magisk] rash.m2k:
Ah ok I see, in which case - how do I go about making changes to the file under /oem/OP/?????
[Magisk] Didgeridoohan:
I don't think you can. Not with a simple Magisk module at least.
[Magisk] rash.m2k:
Oh ok, whats the point of root access then. Surely I should be able to mount the partition as r/w and then edit the file? There must be a way of doing this?
[Magisk] guest4711:
If you are able to mount /oem r/w in TWRP you may use TWRP's integrated filemanager to copy your modified version into place.
[Magisk] Didgeridoohan:
Yes, possibly with a file explorer (I prefer FX). Have you tried?

And just for completeness, that's not at all what Magisk does when magic mounting files or folders. But the details around that can be found on John's GitHub.
[Magisk] rash.m2k:
I've installed FX explorer (https://play.google.com/store/apps/details?id=nextapp.fx&hl=en_GB) but still doesn't work, I am able to mount the filesytem as r/w or at least thats what FX thinks, but then not able to save the file with my modifications
[Magisk] Didgeridoohan:
Then you've got other issues and are probably better off looking for help in your device's forum instead.
[Magisk] rash.m2k:
Np, thanks for you help! And the quick replies, much appreciated! If if do get it working I'll report back.
[Magisk] zgfg:
Tried the latest Canary MM 294 but now it fails to me to hide/repack MM (with Play Protect Off or On)

It worked with 293 (incl. custom renaming, with Play Protect Off) and I was curious to test 294 due to the Changelog
[Magisk] pndwal:
Further to this:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83341897

- Magisk Manager will no longer show confusing/useless installation options.

https://mobile.twitter.com/topjohnwu/with_replies

[Android 4.4 and higher supports Android Verified Boot (AVB) through the optional device-mapper-verity (dm-verity) kernel feature, which provides transparent integrity checking of block devices.

DTB = Device Tree Blob

DTBO = Device Tree Blob for Overlay] PW
[Magisk] Philnicolls89:
Hi mate, i have an s10+ and it has been rooted with Magisk since day 1 so maybe I can help.

First this sounds like a possible firmware/TWRP incompatability issue and not magisk. What exact firmware version are you using?? Eg I am running CTF1 which is june 2020 security patch. Also I am assuming you are on ians TWRP so what TWRP version are you using? 3.3.1 has multiple releases eg 3.3.1-1, 3.3.1-2 and so on.

I've also attached a link to the TWRP thread encase you haven't already been there, the first few pages are definitely worth a read.

https://xdaforums.com/galaxy-s10/development/recovery-twrp-3-3-0-galaxy-s10-exynos-t3924856
[Magisk] monicaONxda:
Root+Encyrption works on system-as-root partitions (A/B, Galaxy Note 10 etc.)!

Many thanks pndwal! The rooting worked with the official Magisk "system-as-root"-guide: I have OEM-unlocked the stock ROM, encrypted it (set lock screen passphrase), patched the stock-AP file with Magisk and flashed it back with Odin (incl. BL, CP, Home-CSC) and wiped data in recovery. The encryption was lost afterwards (because of the wipe?), but I encrypted it again (on the still rooted system!) and it worked! I know have root+encryption on a Note 10!

I assume if I now flash the TWRP recovery image it won't work (bootloop etc. since TWRP can't read the partitions)?

I don't need TWRP anyway, but how I can flash zip files, e.g. to change the splash screen? Can I do this with the stock recovery or Odin?

---------- Post added at 02:08 PM ---------- Previous post was at 01:48 PM ----------

Many thanks pndwal! The rooting worked with the official Magisk "system-as-root"-guide: I have OEM-unlocked the stock ROM, encrypted it (set lock screen passphrase), patched the stock-AP file with Magisk and flashed it back with Odin (incl. BL, CP, Home-CSC) and wiped data in recovery. The encryption was lost afterwards (because of the wipe?), but I encrypted it again (on the still rooted system!) and it worked! I know have root+encryption on a Note 10!

I assume if I now flash the TWRP recovery image it won't work (bootloop etc. since TWRP can't read the partitions)?

I don't need TWRP anyway, but how I can flash zip files, e.g. to change the splash screen? Can I do this with the stock recovery or Odin?
[Magisk] pndwal:
Glad it worked. :good:

My understanding is that wiping /data doesn't remove encryption, but formatting does. Did you in fact format /data?

Not sure, but I think you need custom recovery to flash zips. I think this should install fine, not bootloop etc, and may be able to flash zips from portable storage formatted as (or usb). If you have non-encryption compatible TWRP, I think it it simply won't see os /data.

This is off the top of my head and I don't have Samsung or your architecture, so I may be way off. PW
[Magisk] thearmeddiyer:
Thanks for the reply, and yes I have determined this is an issue with twrp and not magisk as right now I am running magisk only and have no issues. I am using the latest August firmware which is CTG4. I have tried installing 2 versions of TWRP the first was using the TWRP app and downloading the latest than prepatching with magisk prior to flashing it. The second time I used ianmacd's 3.3.1-101. Both times everything worked fine except for the camera. I started a thread over in questions and answers titled "wiped cache now no root" which is more detailed of my experience. And I will head over to the thread you linked to see if I can find any more information.
[Magisk] zgfg:
MHPC Magisk module (new one), it has an option to force old/good Basic attest for CTS - to pass CTS and SafetyNet (mentioned many times here)

If needed, find the XDA thread for MHPC for more info
[Magisk] monicaONxda:
Yes, I formatted it (factory reset) after flashing with Odin, as described in your guide. And I was wondering that encryption after rooting worked, but it did! :)

Re. TWRP maybe I will give it a try (and flash the image via ADB). If I should get a bootloop can I just flash (via ADB) the Magisk-patched boot.img and recovery.img? B.t.w. I also had a boot loop after the rooting process and after I have installed Busybox and Riru/EdXposed in Magisk, but after flashing the fully patched AP (and stock BL, CP, CSCHome) with Odin again, it solved it (and I kept all data!)...

---------- Post added at 03:41 PM ---------- Previous post was at 03:01 PM ----------

Thanks for the hint! I alread checked this module, but my device is not listed! I am not sure if I can use a similar device...? Do you know? Does it depend on the Soc?

---------- Post added at 03:43 PM ---------- Previous post was at 03:41 PM ----------

Thanks for the hint! I alread checked this module, but my device is not listed! I am not sure if I can use a similar device...? Do you know? Does it depend on the Soc?

---------- Post added at 03:46 PM ---------- Previous post was at 03:43 PM ----------

Thanks for the hint! I alread checked this module, but my device is not listed! I am not sure if I can use a similar device...? Do you know? Does it depend on the Soc?

---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------

Thanks for the hint! I alread checked this module, but my device is not listed! I am not sure if I can use a similar device...? Do you know? Does it depend on the Soc?
[Magisk] zgfg:
Device does not need to be listed.

Don't look to the fingerprint option.

Just choose the new option for CTS and follow - to replace few ro.product.* props (MHPC will care which ones) to something, it can be "Unkown", "Undefined", "xyz123" (without quotes) or anything 'meaningless' to trick the G that it doesn't recognize that your device actually supports Hardware based attest, and to use instead the old Basic mode where Magisk can hide that Bootloader was unlocked

See:

https://github.com/Magisk-Modules-R.../master/README.md#force-basic-key-attestation

That's all you need for stock firmwares.

Ofc, first of all, Magisk hide option must be enabled

And pls edit your post(s) to remove duplicates
[Magisk] monicaONxda:
I've tried this (activated "Force BASIC key attestation" and custom props ("xyz123") at "default boot stage") but still SafetyNet failed after reboot !?
[Magisk] pndwal:
Yes, any device not on Google's list of devices currently stated for hardware attestation should force Basic Attestation. Do this only. (Use a Samsung device to keep Galaxy Store etc). Then check attestation type used with Canary Magisk manager. If you're on Basic but still fail you have another problem.

...and please remove duplicate posts on previous page! :good: PW
[Magisk] zgfg:
Magisk hide is enabled in Magisk Manager?

Disable all other modules to make sure it doesn't interfere

Btw, do you really have stock ROM - this solution is only for stock (mentioned all that in earlier posts)

In case of custom ROMs, you need to use fingerprint options
[Magisk] dswwong:
I have just upgraded to oxygen os beta 17 for my op7p.

My problem is I could not find the font changer module in my magisk 20.4 version which I installed.

Any advise on this issue is most welcome.
[Magisk] monicaONxda:
It works !!! (if Magisk is hidden - Sorry I thought it was - already set an alias name some days ago, but somehow the witch was off again!! I also have the Busybox module installed without problems...) :laugh: Thanks again!
[Magisk] Didgeridoohan:
For various reasons Fontchanger was deleted by its developer. It is no more...
[Magisk] zgfg:
Good, now check in Google Play if Device is certified

If not:

- Airplane On

- Settings, Apps, Show System apps and for Google Play app and Services, and Google Services Framework delete Cache and Data

- Reboot, Airplane Off and give some time for Playstore to re-sync
[Magisk] monicaONxda:
I have de-Googled the device to a great extend and only have G Play Services and GSF left, but not Playstore. All banking apps and other apps are running without problems.. Nevertheless I have re-installed (enabled) Playstore but didn't login (don't have a Google account) - but when I clicked on the 3-dot menu there was a message under settings on the left bottom corner that "this device is not certified by G.." which disappeared, after clearing the caches/data and rebooted as you described... I also scanned with Play Protect, but nothing showed up...No status is shown (neither certified nor not certified)...Oops...just discovered, that i didn't whitelist GPlayStore on my firewall...ok....so now it says in play protect: "no problems found"..."recently scanned apps: a, b, c..+42 more..., "Play protect regularly checks apps...blabla..." and "learn more"....That's it, no explicit certification... Under settings also nothing mentioned about certification status. (just Playstore version etc.)....Aahhh!!...after several app shutdowns and re-openings under settings now there is:" Play Protection Certification, Device is certified"!!! Hallelujah !!! :D
[Magisk] dswwong:
So there is no way to change font for now?
[Magisk] HippoMan:
This is a great accomplishment! Kudos!

In your recent messages, you described what you did in general terms. However, would you be willing to post a more detailed "cookbook" of all of the steps that you took to convert your standard, Google-infested apparatus into the certified, SafetyNet-passing, de-Googled device that you're now enjoying? ... i.e., what software you downloaded and installed, what commands you issued, etc.?

I know that such a detailed document could take a lot of time to create, and I certainly understand if you prefer not to write it. But if you happen to be willing, that result would be greatly appreciated.

In either case, thank you!

.​
[Magisk] suhaibahmad:
Log file for a banking app not working

One of my banking app is not working ,its log says :

08-26 05:48:37.880 740 767 I Magisk : proc_monitor: [com.eaccess.mcbmobile] PID=[25849] UID=[10336]

08-26 05:48:37.882 25867 25867 D Magisk : hide_policy: handling PID=[25849]

08-26 05:48:37.882 25867 25867 D Magisk : hide_policy: Unmounted (/sbin)

G

Can anyone figure it out please?
[Magisk] Tulsadiver:
There are modules for specific fonts. If you have a font you like, put them in a module. Usually they are in system/fonts, sometimes some are in system/product fonts or both. Example. Storopia
[Magisk] [DarkGUNMAN]:
Due to the Starling Bank app detecting 'Xposed Installer' by name, I am wondering if it is possible to install it as Magisk module?

I tested this by disabling the Xposed Magisk module - Starling opened up fine. Installed the Xposed Installer app, it tripped the Starling security.

If the Xposed Installer can be activated/deactivated as a Magisk module, this would help immensely.

Stock Galaxy S6 Edge+ ROM
[Magisk] dswwong:
How about comic sans? Can I get this from anywhere?
[Magisk] monicaONxda:
How to pass safetynet ("ctsprofile:true") and achieve "google certified device"

sure! one hand washes the other :) :

how to pass safetynet ("ctsprofile:true") and achieve "google certified device" with rooted phone (tested for note 10+/exynos):

- root device

- install latest magisk

- hide magisk in menue

- install latest magisk module "magiskhide props config" (mhpc)

- install/use a terminal emulator such as termux

- open termux

- type "su" (super user)

- type "props" (starts mhpc)

- type in props menu "2" (FORCE BASIC key attestation)

- type in props menue "5" (add/edit custom props), select new custom prop and any device name (abc123, xyz etc.") and select "default boot stage"

- reboot

=> in magisk you get now safetynet "ctsprofile:true" !!!

(if not, make sure magisk is still hidden in settings, reboot and repeat above!)

- install temporarily playstore (no g-account needed!) - you can delete it again afterwards

- deactivate all networks/internet (e.g. airplane mode on)

- wipe/clear cache and data of all g-apps, especially g-services framework, g-play services, g-playstore (in android system/app settings)

- reboot

- airplane mode off

=> under playstore settings (with internet connection) you get "play protection certification, device is certified" !!!

(if not, repeat above, scan device with g play protect in playstore, wait... it can take 1-30 minutes until g scanned all apps...)
[Magisk] HippoMan:
Thank you very much!!!

You mentioned doing a temporary installation of playstore, and this implies that it didn't previously exist on your device. How did you get your device into a no-Google-software state to begin with? Did you just install a standard ROM and no gapps? Or did you install some sort of microG-based ROM? Or did you manually remove all of the Google software? Or what?

I apologize if I overlooked something which explains this.

I'm on a OnePlus 7Pro (GM1917) and am using the stock OOS ROM (OOS 10.3.4 in my case), and it comes with its own gapps. I guess I would have to either use a different ROM or else manually remove all of my gapps ... correct?

.​