yashsingh1/xdaforums huggingface dataset:
[Magisk] zipsu:
It's good practice to do a nandroid before magisk updates *just in case*. Have you tried using magisk uninstaller? Even if you dirty flash the rom, it only wipes the boot partition, but anything magisk saves to /data remains unless you wipe that as well. You could also use adb: "adb uninstall com.topjohnwu.magisk" to remove the manager app, some magisk files are saved in /data/adb as well (magisk.img and magisk.db) You can back up magisk.img in some other directory and recover it later if you'd like to keep your modules and their settings without having to start from scratch later.
[Magisk] shneor:
Magisk Update Boot Problem

Thank you for your quick reply. I have not installed any other Magisk modules. I have used adb, but it has been awhile. Can I use it in recovery mode? I don't think it will run in a hung boot. I have downloaded the Magisk uninstaller, just feeling very shaky right now. Would removing the manager fix my boot problem?

I did have a nandroid and a full Titanium backup on my SD card, but they are not showing up.

I think I'm done for tonight, can't think straight. I'll work on it tomorrow. Thank you again, if you have any more suggestions, I'm all ears.
[Magisk] zipsu:
Magisk uninstall restores original boot, removes manager and all residuals (assuming everything goes right) essentially giving you a clean slate, can install magisk again afterwards.
[Magisk] saccentekennedy:
Fwiw, I was able to successfully install 18.1 last night after what happened last week. OnePlus reissued Open Beta 4, so I updated to the new version from the old one and installed 18.1 at the same time using the MM to install to inactive slot, and it worked. I DID take a Nandroid backup this time first, though!

Not sure what the problem was and what solved it, but my guess was it was something about OB4?
[Magisk] Valeryan24:
Hi, thanks for the answer ! I could'nt post a screenshot, but I well had your module MagiskHide Props Config v3.0.3 installed. I read the documentation, installed Termux.

Command "getprop ro.build.fingerprint" returns :

google/angler/angler:8.1.0/OPM7.181205.001/5080180:user/release-keys

Without "__2018-12-05" at the end : is it what causes ctsProfile to fail, and if yes, how can I modify it please ? :confused:

If not, what could it be ? Or should I all reinstall ? It worked fine until Magisk 18 (with Manager 6) and the same phone, just now it fails. In Google Play option it appears as certified and I can still update my apps from there.
[Magisk] MikeYT22:
I'm running Cypher OS on my p20 pro and i installed latest magisk manager and flashed latest magisk zip wia twrp(twrp is encrypted so i need to use adb push to flash it) when flashing everything goes well but when i reboot into system in magisk manager says that magisk is not installed. Any help? ROM is Cypher OS 7.0.0 running on android pie.
[Magisk] chipyy94:
Sparkasse banka app wont work

Could anybody help me with sparkasse bank app.. I have oneplus 3t with original rom, with unlocked bootloader. I also installed magisk so i could run this sparkasse bank app which is called m.stik. But even with magisk wont work, so i am beging for help :)

I also hide bank app in magisk hide, but it doesnt help...
[Magisk] DriFtyZ:
Turned out i installed a faulty module that broke magisk modules not to load any modules on startup. A fresh wipe reinstall of rom, magisk and all the modules except the particular faulty one (a ported dolby atmos module) fixed the issue and magisk was working fine and smooth.

---------- Post added at 02:59 PM ---------- Previous post was at 02:54 PM ----------

Did you toggle to hide the particular app from the magisk hide section? Also some apps search the phones data for installed packages with the word "magisk" included in the name and they are blocking access to them therefore you may want to select the option to repackage magisk manager with a random package name from magisk options. If you did both of the steps above then the app is using a method to identify root/magisk existence that magisk is unable to hide from it.

Edit: You may also need to hide google play store amd google play framework from the magisk hide as well. Try that and let us know
[Magisk] mkol:
Magisk 18.1 does not allow root access (installation via TWRP is successful, but the Magisk Manager reports that Magisk is not installed) on Umidigi F1 (Android 9.0), but version 17.3 works correctly.
[Magisk] guest4711:
Hide MM by repacking it to a random name (there's a menu entry in settings for thid purpose). And install MagiskHide Props Config module from download page in MM.
[Magisk] Didgeridoohan:
"__2018-12-05" is just the module syntax, it's got nothing to do with the regular fingerprint. If you need further help, grab the module logs (instructions in the documentation) and post in the module thread.

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

[MENTION=8123928]MikeYT22[/MENTION] and [MENTION=1547481]mkol[/MENTION] You guys might be affected by this (but it's hard to tell from the way you describe the issue):

https://didgeridoohan.com/magisk/Magisk#hn_Updating_from_v18.0_to_v18.1
[Magisk] MikeYT22:
Can i shoot you a dm explaining my situation?
[Magisk] Didgeridoohan:
I'm assuming that the information in the provided link did not apply in your case then...

I would prefer if you post here in public, since that way it could help others that find themselves in the same situation.
[Magisk] MikeYT22:
Ok. So i didnt have magisk allready installed. this was first time flashing and installing magisk and magisk manager. The flash didnt show any issues but after reboot root was gone(magisk manager said: magisk not installed)
[Magisk] Didgeridoohan:
Edit: actually first thing you should check is to make sure the Manager isn't installed to external or adoptable storage. That will cause this kind of issues as well.

Ok... A log from the installation would have been good. Try starting over. Uninstall the Manager (there's no need to install it first if you're gonna flash the Magisk Zip in recovery, it'll be installed automatically) and then flash the zip again. But, this time save the log afterwards and post that for analysis. Here's some info on how to provide said log:

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

If that still doesn't work you could try the patched boot image method (and don't forget to save the logs in case you need it):

https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
[Magisk] akxak:
Downgrade to Magisk 17.x, this thread and Github is full of reports on that with no solution or even reply from the author so far.
[Magisk] lohanchien:
He's acknowledged the issue and did specify that 18.1 doesn't include any Magisk Hide changes. Hopefully 18.2 (or 19?) comes out soon with fixes.
[Magisk] Pkt_Lnt:
You need to check the correct place for his comments:

https://twitter.com/topjohnwu
[Magisk] akxak:
How many places should one check... that's what Github is for.

And looked through his posts there till Magisk 18 release and found nothing on that particular problem.
[Magisk] Ps24u:
Can Magisk be installed on Xperia Z1 Compact with locked bootloader?

I currently use a prerooted ROM with supersu, and it works just fine. Bootloader is still locked (as sadly "bootloader unlock allowed= no" for my device)

Android version is 5.1.1. SuperSu 2.82 is installed in "system" (old way, not systemless).

I wanted to switch to Magisk, if possible so ran unSU.zip and tried to flash Magisk latest version via TWRP.

Flashing Magisk failed because of Sony ELF and told me to run the installation via Boot Bridge by AdrianDC.

But Boot Bridge apparently needs an unlocked bootloader so it's a catch 22 situation it seems.

Is there any solution for this specific case? Please lmk.
[Magisk] Pkt_Lnt:
Obviously top john wu does not share your opinion. :D :cyclops:

Seems most communications between those actively developing are done in private. Remember top john wu is a full time student working on a masters degree, and likely does not have time to hang out on various websites, social media, github, etc. chatting with users. That is why there are a dozen or so great supporters in this forum who work directly with top john wu, and help users like you and me. :good:
[Magisk] akxak:
Yeah, but that let's people miss relevant information like his Patreon page to support his work.

Any link to that specific statement on Twitter, I cannot find it.
[Magisk] Didgeridoohan:
The fact that he opened the GitHub issue about this (#907) means he's aware. And you can be sure that there is constantly work being done (it's just that there are tons of prioritisations that need to be made, as stated in the latest release notes).

The best way to see what progress is being made is to check out the commits on GitHub... You don't even need to know code, since the commit titles usually are quite descriptive, and sometimes it's even accompanied by a more detailed description. If you look at the last few commits you'll see that MagiskHide is being completely reworked, something that very likely will have a direct influence on the problem at hand...
[Magisk] brown1178:
Is there already a fix or a workaround, for Oneplus 6 only showing black screen after updating to 18.1 and rebooting?

Today I wanted to update to OOS 9.04 and because the last two updates ended in a bootloop, today I wanted to uninstall magisk and all substratum files - to get the device without any modifications. But even uninstalling magisk with the uninstall option in magisk manager caused the device to stuck in a black screen right after the "unlocked bootloader" warning...

Am I doing something wrong?
[Magisk] akxak:
I saw that rewamp of MagiskHide in the release notes of 18.0 and suspected the trouble in that rework.

I am aware how much work this is and that beside working on his master's degree... that's why I liked to see the patroneo page, allowing to honor the time he puts in.

I'm happy with 17.x right now, a single statement like "problem is known, we're working on a fix and let you guys know" would have been good.. to point people running into to and to wait for an update when it's solved.
[Magisk] chipyy94:
Thnx for help, i wiped my phone ( left only internal storage) and freshly instaled oxygen os. Then i installed Sparkasse bank apk and i activated it. After that i installed magisk + magisk manager, ofcourse i checked magick hide and also add this apk to hide from root. And now the apk opens and i hope that also work correctly ( didnt try yet) . So that is the solution how i fixed my problem with bank app.
[Magisk] DualJoe:
When i copy 'libjni_latinimegoogle.so' into /system/lib it is vanished after reboot. Where do i have to place the file (without creating a module) so it remains persistent (/sbin/.magisk/mirror/system/lib is not writable)?

Edit: Regarding the docs it should be placed into '/data/adb/magisk_simple/system/lib' but the file is not there after reboot.

Any ideas?
[Magisk] RebelLion_:
I noticed an issue with Magisk and my custom kernel. I had no issues until I upgraded my toolchain to Linaro's 7.4.1 and flashed with Magisk 18.1. My touchscreen stopped working, and I could only fix it by flashing Magisk 18.0. I'm not sure what the issue is or how to get a log of that, however I can attempt to provide a dmesg if needed. And my kernel source to see if there's an issue on my end

https://github.com/RebelLion420/kernel_perry

'rebel' branch
[Magisk] zipsu:
That's the whole reason why magisk exists, to avoid changing anything in system, instead it modifies boot.img to load itself before rom even starts. Supersu uses the oldschool way of rooting (unless you use its newer systemless variant) which is why you're rooted. Afaik, there is no non-systemless build of magisk. You need to get rid of that carrier lock to allow bootloader unlocking, which costs like 5-10€, you may also try contacting the provider you bought the phone from, some of them are willing to provide unlock codes for devices that are "fully paid for" or try the same with Sony mobile support. It's either this or.. a new phone.
[Magisk] jcmm11:
magisk_simple will only replace an existing file, not add a new one.

You need to create a simple module structure. Something like:

Create /sbin/.magisk/img/libjni/

In there place an empty (0 byte) file named 'auto_mount' and a directory system/lib/

Place libjni_latinimegoogle.so in that directory

Make sure all permissions are correctly set

Reboot

(You can optionally add and fill in a module.prop file, but it's not absolutely required)
[Magisk] Ps24u:
Thanks, so you're confirming Magisk can NOT be used on devices with locked bootloader?
[Magisk] DualJoe:
Works, thanks. :good:

The most easy way probably would have been to copy the file in TWRP to /system. But who likes easy ways if you can learn Magisk...
[Magisk] jcmm11:
Normally true, but I'm curious - how did you install TWRP if you have a locked bootloader?

The bigger issue here seems to be your kernel format. If you could somehow successfully patch the kernel you should be able to flash it with TWRP. That's a big if though.
[Magisk] DualJoe:
Probably just an exploited stock rom. Any flashed kernel/recovery probably will be refused by the bootloader.

Never mind... :)
[Magisk] guest4711:
No, this way you change the chksum of the partition... To avoid that you mount a file into this partition using magisk. No chksum mismatch, no problems with OTA, less problems if something is wrong with the file, easy activating and deactivating of your change... (and no need to move an old file out of the way).
[Magisk] nickname_marco:
I am unable to install latest Magisk manager; device is a 3T running stock OxygenOS 5.0.8

A bit of background info.

I flashed several times Magisk on a couple of 3Ts and everything was working fine. On a 3T, I used to have OOS 5.0.6, Magisk 17.x and Magisk manager 6.x.

At first, I updated to 18.0. After a few days, I updated Magisk manager to 7. Installation went fine but the app drawer reported I had two Magisk manager installed. One of them couldn't load properly but it was the v7 interface, the other was running fine but was the older Magisk. Going out of the drawer and getting back in, Magisk v7 disappeared.

So I booted to TWRP, uninstalled and reinstalled Magisk, but once in OOS I had the same issue described above.

I took the chance to uninstall Magisk manager and then update to OOS 5.0.8 but I now I am totally unable to install Magisk v7 as the installation doesn't go through.

Any advice please? I would avoid to do a fresh install but if I don't have a choice...
[Magisk] DualJoe:
Yes, you're right. But i'm on LOS with permissive selinux anyway. No need for integrity conformance,

Any error messages in syslog?

Maybe look in /data/app and /data/data for com.topjohnwu.* folders, delete them manually and reboot. Also look in /data/dalvik-cache.
[Magisk] Ps24u:
I use what is seemingly called "fake recovery" as my bootloader cannot be unlocked.

From this guide:

https://xdaforums.com/sony-xperia-z1-compact/general/beginners-guide-root-backup-ta-ubl-t3816145

Please see the big point 6.

I'm not sure why Supersu can be used in this way but not Magisk..

When I use Boot Bridge by AdrianDC + latest Magisk stable build, as instructed by Magisk itself when attempting to flash the Magisk zip directly from TWRP, the patching of the kernel is actually reported as successful (in TWRP log), but the device just won't boot afterwards (not even sony logo at start but black screen with blinking led, only reflashing original kernel revives it).
[Magisk] DualJoe:
Because your kernel and recovery partitions are protected by the bootloader. They are digitally signed/verified. The system partition is not.

Your "fake" TWRP seems to reside in the /system partition (nice trick).
[Magisk] jcmm11:
I've been running unlocked bootloader's so long I forgot the details but I believe [MENTION=4293606]DualJoe[/MENTION] is correct. Which leads to my final question. Why don't you just unlock your bootloader? Apparently Sony provides a free mechanism to do so.
[Magisk] Ps24u:
Some Xperia phones bought from certain carriers have "bootloader unlock allowed: No" and in this case there is just no way to do it :S

Such a bummer not being able to switch to Magisk, it didn't occur to me there were still instances where SuperSU is irreplaceable.
[Magisk] jcmm11:
If the phone is paid off I would go and ask the carrier. If they say no I would become an incessant pest until they said yes just to get rid of me.
[Magisk] Didgeridoohan:
Try this:

https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_install_the_Magisk_Manager

And just for those who are curious, here's why the described occurrence happened:

https://www.didgeridoohan.com/magisk/Magisk#hn_Updating_from_v18.0_to_v18.1
[Magisk] zputnyq:
Afaik "bootloader unlock allowed: No" is only to notify that the bootloader hasn't been unlocked yet. Have you tried to unlock it ?

Since in my xperia which comes with Canada carrier is unlockable
[Magisk] shneor:
Still Stuck on Magisk Update

I redownloaded the uninstaller, copied it to my sd card. and tried to flash it. These are the messages I received:

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

! cannot access /data, please uninstall with magisk manager

unmounting partitions

updater process ended with ERROR: 1

Error installing zip file '/sdcard1/magisk-uninstaller-20190204.zip'

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

Of course, I can't get to magisk Manager because my device won't boot, except to recovery.

I tried to use adb; adb devices worked just fine but the uninstall command returned what I think are Linux errors, which I may be able to solve. I could wipe /data. The only item in the data directory (as opposed to the partition)

is Titanium. But that may not solve my problem. I'd appreciate any ideas to help me fix this.

Edit: I tried to run "adb uninstall com.topjohnwu.magisk" but it returned this error:

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

/sbin/sh: pm: not found

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

I ran the command from the directory in which adb is located.

I think I may just have to wipe everything, much as I hate to do that. Any other suggestions are welcome.
[Magisk] Schmand:
Honor 8x EMUI 9 Beta

Hello,

I have a Honor 8x in EMUI 9 Beta (Official from Honor) and want to install Magisk v18.1.

The install process runs without an error. After installation there is no Magisk Manager App, so I installed it separately. In the Manager App is an error that Magisk is not installed. Any ideas to fix that?

Regards

Schmand
[Magisk] martyfender:
https://xdaforums.com/showpost.php?p=78901445&postcount=31365
[Magisk] MikeYT22:
Where can i check that?
[Magisk] Ps24u:
I'm afraid you're wrong, "Unlock allowed: No" means it cannot be disabled. At all.

Different carriers have different policies. Mine sucks, and doesn't care :crying:
[Magisk] zputnyq:
Oh yes, my bad.

It's been 2 - 3 years, I unlocked it so I forgot about it
[Magisk] y2knarayan:
Nothing to do with Magisk. Its about Google Pay
[Magisk] akxak:
Really? Look through this thread and the respective bug report... I'm on Magisk 17.x and Google Pay and everything else is working fine.

Magisk 18.x has a known and yet not solved problem with MagiskHide...

Solution: Downgrade to Magisk 17
[Magisk] vergilbt:
Did downgrade to Magisk 17 but unfortunately GPay isn't working working again...
[Magisk] akxak:
Did you try to delete GPay data (reinstall?).

GPay on my phone with Magisk 17 runs fine.
[Magisk] vergilbt:
I did ALL...

Was deleting data, app, Magisk, manager, tried hide and so on...

Since last update to Magisk 18 I'm not able to activate PayPal in GPay...

Weird
[Magisk] ShabyDaby:
i got verification failure after installing magisk after updating android to 9.0 Pie
[Magisk] melonrasaduren:
how to downgrade it safely without bootlop and lose any data?

Mine is 18 and cant access my banking app

big thanks
[Magisk] mcampbellsmith:
Google Pay card activation fails - Pixel 2 stock

Same issue here with Google Pay. I'm on stock Android 9, Pixel 2 without TWRP, unlocked bootloader, Magisk v18.1 and Magisk Manager 7.0.0.

When I try to activate the card in Google Pay, this is what I see (cleared log prior to launching GPay)

02-15 18:10:19.336 710 1093 I Magisk : proc_monitor: com.google.android.gms/.tapandpay.tokenization.TokenizePanActivity PID=[10160] ns=[4026534076]
02-15 18:10:21.576 710 1093 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[10213] ns=[4026534077]

Google Pay is 'hidden' in Magisk Hide. I've cleared data from GPay, used the ClearDalvikCache4Magisk module and all without luck. I am unable to deselect 'Phone' from Google Systems Framework as GPay does not launch at all without that ticked.

I've also tried with ShellHide without luck.

Any ideas?
[Magisk] HemanthJabalpuri:
Can someone please help with https://topjohnwu.github.io/Magisk/deploy.html#exploits ...

I cant understand what is the summary...

I dont know I have those requirements but tried that guide and managed to get root through system installation in KitKat with below attached zip.. but Magisk Manager force closes when opening...
[Magisk] honorfan:
Hi i don't know why can't i flash some zips

Before i could flash them easily but no i face error

Plz install magisk 13.1 and upper

I even try to flash magisk 18.1 by twrp and pathced boot but still the same issue
[Magisk] Didgeridoohan:
The module is made from an outdated template/hasn't been updated.

https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_install_modules
[Magisk] chinchulin01:
I forgot to say that I repacked Magisk already.

I'm afraid I have never used the shell for this. Do you mean using it with the phone connected to the computer or directly on the phone? Can you please explain? Sorry for the n00bness.
[Magisk] RebelLion_:
[MENTION=4667597]Didgeridoohan[/MENTION]

I noticed an issue with Magisk and my custom kernel. I had no issues until I upgraded my toolchain to Linaro's 7.4.1 and flashed with Magisk 18.1. My touchscreen stopped working, and I could only fix it by flashing Magisk 18.0. I'm not sure what the issue is or how to get a log of that, however I can attempt to provide a dmesg if needed. And my kernel source to see if there's an issue on my end

https://github.com/RebelLion420/kernel_perry

'rebel' branch
[Magisk] guest4711:
The finetuning of the module is done on shell. If you don't have an entry "terminal" in app drawer you can try to enable it in developets setting. If you don't find it install Terminal Emulator for Android (Access Android's built-in Linux command line shell. Unleash your inner geek!) - https://f-droid.org/app/jackpal.androidterm -. Open the terminal and enter

su
props

. Follow the instructions in the menu displayed.
[Magisk] MarcoD14:
Good afternoon. Maybe it's a dumb question, but Magisk Modules does work with a encrypted ROM? Cause I'm using the Pixel Experience encrypted on my Redmi Note 5 and every module for camera API 2 it's not working, i can install it, but it's not getting recognise by gcam or every other app that requires Api2/hal3 support, someone can help me? Many Thanks in advance.

Update: After trying other modules, now it's saying that is unable to unpack boot image, now even Magisk itself is lost, so... should format and never encrypt my phone again? :(
[Magisk] Didgeridoohan:
I know nothing about kernel development... If you can find what's causing it and it's actually a confirmed problem with Magisk you should open a GitHub issue.
[Magisk] ippoglosso:
Magisk hide (1.8.1) d'ont work with banking 6.2.3 (Credit suisse)

Inviato dal mio HTC U11 utilizzando Tapatalk
[Magisk] guest4711:
Did you try everything suggested in this fine guide https://www.didgeridoohan.com/magisk/MagiskHide , especially hiding MagiskManager itself by repacking it into random named app?
[Magisk] Kglim:
What is the relative between spotify and safetynet?

When im playing music with spotify, my both safetyNet checks fail.

Is this thing cause of systemized spotify??