yashsingh1/xdaforums huggingface dataset:
[Magisk] wirelesskebab:
Vendor is not displayed under Mount option, only the following is displayed: "System, Data, Cache, Micro SDCard, USB Storage" vendor is not displayed. I am on a Samsun Galaxy Tab S2 6.1 (2015) SM-T710, on TWRP 3.1.0-1.

Everything after 11.0 pretty much didn't give root until minutes after booting into the system, same for 12. I dirty flashed 13 over 12 (had problems, but it flashed) however, I re-flashed the same stock image and am now unable to flash 13 with even the older version of TWRP.

Mount is just a front facing part of the GUI, surely it can be done from the TWRP terminal? Vendor can be seen in the top most folder.

Please assist if possible, thank you.

Edit: I will post logs if I can, thanks.
[Magisk] blackthund3r:
Thanks for the update!

Would it be possible to compile OpenSSL statically to run under TWRP, then generate a new certificate and a random package ID at install time? Then each person would get a randomly named Magisk Manager app with a new signature?
[Magisk] DB126:
Wrong thread

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
[Magisk] seijuro572:
does this work on treble oreo roms ? or do you need to download a specific one for it to work?
[Magisk] Paz9:
i notice the same
[Magisk] Artim_96:
Read latest release notes and try it for yourself. If it doesn't work make a proper bug report
[Magisk] osm0sis:
Okay, my updated 1.29.1 with the broken gzip rolled back to its most recent working commit is now up on the module repo. It's the only busybox 1.29.1 available with that working right now. :D
[Magisk] kunaldas65:
is every module needs update to work with 16.6 or 16.7 or old module will also work???
[Magisk] jcmm11:
Most will work. Some very old ones won't. If they worked with 16.3 they'll work with 16.7

16.3 is where the symlinks, which had been left in for backward compatability, were removed. Most modules using the old template stopped working at that point.
[Magisk] Aelsherbiny56:
Pls ...... Am now on 16.7 ... So If there is an update for magisk (stable build or beta) ,,, how should I update magisk ?(what is the steps for the best way to do that?)

Or I have to completely uninstall it then install the new build ..

I will be so thankful..
[Magisk] DanGLES3:
Change the update channel on your magisk manager options to beta or keep it stable if you only want stable builds,the app should notify you about updates and prompt you to either install directly or download the zip so you can flash on twrp,uninstalling is not required,you can just flash the newer versions on top of each other
[Magisk] JediBrooker:
Magisk Hide is not working for the Maybank app. I've tried both stable 16.0 and 16.7 versions and both with and without modules. I'm at an impass with my knowledge on what else I can do to troubleshoot. Attached is my log.
[Magisk] martyfender:
Have you tried hiding the Magisk Manager app in settings? After doing this you may also need to delete the data and cache for the app, in the Android app settings.

Also, have you looked at the suggestions in this guide?

https://www.didgeridoohan.com/magisk/HomePage
[Magisk] JediBrooker:
Deleting data and cache plus a reboot did the trick. I'd already enabled hiding the app.

Cheers!
[Magisk] carlese:
Hi guys, I installed latest 16.7 using the update feature and now I don't see the download modules option inside magisk, I only see the modules section.. Also, on the first page, I only see the build number and nothing else..
[Magisk] guest4711:
Make sure you have a working internet connection before opening MagiskManager (and you did not block internet access for it).
[Magisk] carlese:
That was it, I had no data, rebooted again and now it works.. Thanks!
[Magisk] ultradj83:
Failed encryption

Dears,

To install Magisk I installed TWRP on SM-A530F/DS and flashed no-verity-opt-encrypt-6.0 and formatted data to let the phone boot.

Well, I'd like to re-encrypt the phone like I've always been doing on sammys after TWRP or Magisk installation, but it doesn't work on this phone.

No matter if it's Nougat or Oreo, applying encryption nothing happens and phone crashes backing to lock screen in a minute.

Any suggestions?

Thanks everybody.
[Magisk] Terrigible:
Try using the enable force encryption option in Magisk
[Magisk] jenslody:
And don't spam the threads with the same question. If it is an issue with the beta you are in the correct thread, but without logs it's useless and not allowed (see the OP).
[Magisk] ultradj83:
Dear,

Magisk refuses the option.

With the help of [MENTION=8235996]meta i[/MENTION]'ve also been checking the ramdisk's fstab, no way...

---------- Post added at 10:34 AM ---------- Previous post was at 10:28 AM ----------

Well,

this is not related to a particular version.

I mean, the force encryption option is rejected on v16 and v16.7, but the issue comes during preparation, before to flash Magisk, that's why I provided no logs.

I posted here cause I think anyone wants to use Magisk with encryption on A8 will find this problem.

It could be interesting to contact no-dm-verity developers but I couldn't find any contacts...

Tks.
[Magisk] jenslody:
What do you mean with refuse.

It should stick if you switch it on before flashing Magisk through the Manager (either directly or if not yet rooted to create a patched boot-image).
[Magisk] ultradj83:
Sorry this is not clear to me...

I tried to enable it with TWRP and Magisk already installed, but no encryption was performed upon reboot.

Do you mean I need to tick it, then to prepare boot image installing Magisk?

Tks a lot.
[Magisk] spaziomilano:
Hi, have a problem with magisk and the last Google pay is it just me. With the Google pay 2.70.204... Magisk failed CTSprofile:( someone help me on this?
[Magisk] jenslody:
Yes, if you already have root, you can tick it and then do a direct install and it should stick.
[Magisk] JW19:
Magisk Manager doesn't open

Lately I've been doing lots of flashing with kernels and ROMs, sometimes problems occur but i just restore system and boot partition with TWRP backup. Since the last time I restored system Magisk manager is failing to open. As a result applications are unable to request for root.

What I've done:

Cleared Magisk manager data and cache.

Uninstalled and reinstalled different versions of Magisk manager.

Uninstalled Magisk with uninstall zip, then reinstall.

None worked.

I have a logcat, however I cannot find an option to add any file attachments here.
[Magisk] ultradj83:
No way, unfortunately it does nothing...
[Magisk] jenslody:
Yes, if you already have root, you can tick it and then do a direct install or prepare a boot-image to flash through twrp or fastboot and it should stick.
[Magisk] adwaitatre:
Magisk gets uninstalled again and again please fix it.
[Magisk] Didgeridoohan:
Please provide a logcat showing the uninstallation happening. Yes, that'll mean grabbing an active logcat until it happens, however long it takes.

You definitely don't need all those (54) apps on the Hide list.
[Magisk] Abolfazl:
I updated to July build on my Pixel 2 and installed Magisk 16.7. Once it was installed I got a message from Magisk that it patched my dtbo.img file and I should reboot. Now upon reboot, I keep getting the "There's an internal problem with your device." message.

Is this a problem other people are having?
[Magisk] Didgeridoohan:
https://xdaforums.com/search/thread/3618589?query=There's an internal problem with your device
[Magisk] Abolfazl:
I followed your instructions.. "In Magisk Manager, "Uninstall > Restore Images" to restore the images, check "Preserve AVB 2.0/dm-verity" box in Advanced Settings, then reinstall Magisk via the app." and I am still getting the message
[Magisk] Didgeridoohan:
Not my instructions... They're from [MENTION=4470081]topjohnwu[/MENTION].

Do it again, and then provide the installation log.
[Magisk] Abolfazl:
Okay here is what I did and it seemed to work. I think issue was that my dtbo was not being reverted to stock. You will need stock boot.img, dtbo.img from the current build you have installed on your phone.

Uninstall > Restore images (if backup was made)

Reboot to bootloader

adb reboot bootloader

Restore stock boot.img (for good measure or if you didn't have backups from earlier)

fastboot flash boot boot.img

Restore stock dtbo.img

fastboot flash dtbo dtbo.img

Reboot phone

fastboot reboot

Go to Magisk Manager and Install by patching stock boot.img (same one flashed earlier)

Pull modified boot.img

adb pull /sdcard/MagiskManager/patched_boot.img

Flash patched boot image

fastboot flash boot patched_boot.img

Reboot phone

fastboot reboot

All done
[Magisk] Vipxpert:
When they said no more /data/adb/magisk.log , they mean no /data/adb/ also !

I'm seriously ! Where is my /data/adb/ ? :(
[Magisk] jcmm11:
If Magisk is installed and working then you should definitely have /data/adb since that's where it stores both magisk.db and magisk.img

So my first guess would be that Magisk isn't installed, or at least not correctly, and isn't working.
[Magisk] martyfender:
I agree, there is no reason you need to hide most of those apps and that could be one of the reasons why Magisk is getting uninstalled?
[Magisk] y2kbugleung:
Hello, it seems I have found a Magisk problem:

https://xdaforums.com/showpost.php?p=77170190&postcount=2789

It seems the magisk.log is re-created every boot, the content of my current magisk.log looks useless to this case.
[Magisk] paarnoutse:
Not sure whether it's related to your problem, but at least make sure that for an encrypted device you use the previous TWRP 3.2.1-1 version, and *NOT* the latest TWRP 3.2.2-0 version.

This because TWRP 3.2.2-0 can't access your Data partition when your device is encrypted (which works OK with TWRP 3.2.1-1).

See https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1268
[Magisk] neekless:
You probably don't need magisk.log. Just post the logs you posted to the flash kernel thread. I'm no expert, but I took a look at your logcat.

Line 522: 07-26 11:01:40.996 1206 1206 I LockSettingsService: Device doesn't implement AuthSecret HAL
Line 523: 07-26 11:01:40.997 1206 1206 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.password.key: open failed: ENOENT (No such file or directory)
Line 524: 07-26 11:01:40.998 1206 1206 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/password.key: open failed: ENOENT (No such file or directory)
Line 525: 07-26 11:01:40.998 1206 1206 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.pattern.key: open failed: ENOENT (No such file or directory)
Line 526: 07-26 11:01:40.998 1206 1206 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.gesture.key: open failed: ENOENT (No such file or directory)
Line 527: 07-26 11:01:40.998 1206 1206 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gesture.key: open failed: ENOENT (No such file or directory)

Line 2850: 07-26 11:01:41.751 1206 1206 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/users/10/gatekeeper.password.key: open failed: ENOENT (No such file or directory)
Line 2851: 07-26 11:01:41.751 1206 1206 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/users/10/password.key: open failed: ENOENT (No such file or directory)
Line 2852: 07-26 11:01:41.751 1206 1206 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/users/10/gatekeeper.pattern.key: open failed: ENOENT (No such file or directory)
Line 2853: 07-26 11:01:41.751 1206 1206 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/users/10/gatekeeper.gesture.key: open failed: ENOENT (No such file or directory)
Line 2855: 07-26 11:01:41.751 1206 1206 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/users/10/gesture.key: open failed: ENOENT (No such file or directory)

I can't tell you what the problem is or how to fix but these lines may be the problem.
[Magisk] TiGuy82:
I had used Magisk Treble 16.4 with my Redmi 4X and AOSP extended with no issues at all... but when I flash 16.7 I can't boot to OS. I get black screen :/
[Magisk] Hitlerzz:
Not able to bypass security when I am trying to play Pokemon GO.... It shows that the os or software is not compatible.... I flashed v16.7 and also added the Pokemon go under magisk hide manually... Still the same issue..... Any help would be appreciated
[Magisk] libin20031116:
Can anyone please tell me why would this happened?I re-flashed Magisk times and times but it still doesn't work . All magisk moudles can't be installed to my phone X_X can anybody give me a hand？Now im Magisk 16.7

It says like this

- Copying zip to temp directory
- Installing Magisk_GALACTIC™ Forced DeepSleep省电模块v1.0.zip
- Mounting /system, /vendor, /data, /cache
***********************************
! /data/magisk isn't setup properly!
! Please install Magisk v14.0+!
***********************************
Failed!
! Installation failed

[IMG="This is hoe it looks"]https://i.loli.net/2018/07/26/5b599f91a77d5.jpg[/IMG]
[Magisk] guest4711:
Please ask the developer of this module to make it compatible with Magisk >= 16

The layout used has been slightly changed...
[Magisk] Oswald Boelcke:
Personally, I think this is the wrong thread for your problem. I suggest to ask here.
[Magisk] libin20031116:
No I means, every moudle i install is quite like this.EVERY.
[Magisk] Dreamer(3MF):
What Is The Current Version Of Flashed Magisk?
[Magisk] libin20031116:
17.7
[Magisk] Didgeridoohan:
[MENTION=7408621]Oswald Boelcke[/MENTION] was not posting that at you, but another user. [MENTION=8010004]guest4711[/MENTION] have given you the answer though. The modules you're trying to install are outdated and needs an update to the current module template.

If you have similar issues installing modules from the Manager Downloads section, that likely means your Magisk installation is broken and needs to be reinstalled.

For future reference, please be as detailed as possible when posting about issues. Check the OP of this thread and here.

And don't link huge screenshots like that. They might look fine on a mobile device screen, but on a computer it takes up the entire screen. It's quite annoying. Use the attachment feature instead.
[Magisk] libin20031116:
alright im sorry & i would never ever do that again and,ihad already re-installed magisk times and times but it still doesn't work at all
[Magisk] Computoncio:
Did you use the uninstall magisk zip or you just flashed the same magisk zip again?
[Magisk] rdmrocha:
[MENTION=4470081]topjohnwu[/MENTION]

In latest Android PPP5 for the Pixel 2, 1671 installs correctly but I cannot setup a PIN. Installing 1660 and then upgrading to 1671 via MagiskManager works as intended

Steps for first case:

- fresh install of PPP5 on walley

- boot to twrp-3.2.2.0

- flashed "FlashKernel v2.57" (tried several, didn't make a difference. Also stayed on stock once, didn't make a difference so the logs have the FK2.57)

- flashed magisk 1671

- boot to Android

- go to settings, setup PIN security, go through the process, confirm OK for the PIN, back to the menu and no change, PIN not applied.

- turn off the screen and on again to verify, no PIN requested.

Steps for second case:

- fresh install of PPP5 on walley (first time I went this route, I just reflashed boot.img but went through everything again to make sure is doesn't make a difference)

- boot to twrp-3.2.2.0

- flashed "FlashKernel v2.57"

- flashed magisk 1660

- boot to Android

- go to settings, setup PIN security, go through the process, confirm OK for the PIN

- turn off the screen and on again to verify, PIN is requested and everything is OK

- go to MagiskManager and trigger the update to 1671 (saved the logs)

- reboot and everything is OK and as expected.

You can find the logs for both runs in the attached ZIP file. Hope it helps.

Thanks and keep up the awesome work! ;)
[Magisk] xunholyx:
You can use it. You just have to disable lock screen first before booting to TWRP so it doesn't ask for a password. That's what I do
[Magisk] JakeDHS07:
My Pixel XL has working decryption on the 3.2.2.0 twrp. Guess I got lucky
[Magisk] Soooperstar:
+1
[Magisk] ch3mn3y:
Where is magisk.img in 16.7? I got stuck on multiple FC's coz of one of Xposed modules, but cannot mount magisk.img with MagiskMount (error 1). When checking /data/ there is no magisk.img. However it's working fine, so it have to be there. There wouldn't be no errors if it wouldn't exist...

Found it in /adb/. Now why error, will ask in module thread...

Is there a way to mount /data/adb/img? All Mount modules I found (Magisk Mount, Magisk Mount & UnMount, Magisk Mount Resize) look for /data/img...
[Magisk] Didgeridoohan:
Mount Magisk zip
[Magisk] paarnoutse:
Correct, but that's not an option in case you're using your device for an Office365 Work account, where in most cases Microsoft Intune Company Portal is required, device encryption is enforced, and also a lock screen PIN is enforced via Device administrator rights for Intune. Disabling the lockscreen PIN requires to disable the Device administrator rights for Intune. However, this can be recognized by Intune and when Intune has no admin rights it will make the (correct...) conclusion that your device is rooted (which was hidden before via Magisk Hide for Intune and for all Office apps). Recognizing root will stop the device enrollment at your company, so all Office365 access for your Work account from your device (Outlook, OneDrive, etc.) will immediately be blocked.

Nb.

Because this has nothing to do with the subject of this Magisk thread, I think better not to discuss it further here.

I'll add some related info in the TWRP 3.2.2-0 Github issue discussion.
[Magisk] jugoslavpetrovic:
Already asked before...

Fingerprint granting doesn't work. Is there any clue why and how to fix it?
[Magisk] rdmrocha:
Check my post https://xdaforums.com/showpost.php?p=77175442&postcount=6236

Also had issues with security (in my case PIN + fingerprint). going with build 1660 to set it up and upgrading to 1671 afterwards fixed it for me.
[Magisk] jugoslavpetrovic:
I don't have fingerprint/pin issues. I was asking about fingerprint root access granting.
[Magisk] Galactus:
edit: wrong thread
[Magisk] Paschfire:
I can confirm, the Fingerprint Authentication option for granting Root access has been broken the past few Magisk updates.
[Magisk] IlD4nX:
To me works with no problem at all... Never had issue on this.
[Magisk] rdmrocha:
Misunderstood your post. On my Pixel 2, running latest Preview5 and with my 1660 to 1671 upgrade path, I have no issues on fingerprint root granting.
[Magisk] Terrigible:
May I know why I can't edit /data/cache?

It's a PITA as I want to detach YouTube Vanced.
[Magisk] Shished:
I have a problem with magisk 16.7. when some magisk modules are installed, rom does not boots and phone reboots to recovery.
[Magisk] kantjer:
LOL, what do you expect from this post.

If you install some modules, on some phone running some ROM you have some problem. You didn't even provide some logs.
[Magisk] Shished:
Maybe someone had similar problems, I dunno.

I tried 3 ROMs - P DP5 GSI, Resurrection Remix GSI and lineageos 15.1 and all of them had similar problem - ROM reboots to recovery by itself. When I removed modules, ROMs booted without problems.

As for logs, I don't know which to provide.
[Magisk] wartomato:
A device would be nice, maybe the modules you flashed... Things like these are more helpful than a global post. (Although I assume that you are on OP6)
[Magisk] Shished:
I'm using leeco le max 2, it recently got unofficial treble support.

I tried YouTube vanced on RR, magicgapps on LAOS.

On P DP5 I had my own module which changed some props and YouTube vanced.

At first ROM booted and everything was fine but after reboot it stuck on boot logo and rebooted to recovery. Cleaning cache and dalvik does not helps.

BTW, I used unofficial installer for vanced from their website.
[Magisk] wartomato:
So, i do not think this is related to Magisk, as YT Vanced causes random reboots and bootloops on other devices too.

And the devs might thank for at least a few necessary Infos...now. :eek:
[Magisk] thecoolkid:
Anyone else having the same issues as me? Preferably Xiaomi's device user's with unofficial Treble?
[Magisk] kfatah22:
I am sure that this is not a bug in Magisk, but my phone only boots with Magisk 14, any newer version causes bootloop, I tried using "no verify opt encrypt" didn't work

I have twrp, honor 8, lineage 14.1.

Any help would be appreciated, please.
[Magisk] _euphonic_:
Xiaomi mi6 SAGIT bootloop after install Magisk

Hi You All

I have issue:

After installing Magisk 16.4 have all the time a bootloop and nothing moving on

But when install Magisk-uninstaller-20180719 can boot system normally

I use:

Xiaomi mi 6 6/128 ceramic - SAGIT (unlocked fastboot)

RR-O-v6.1.0-20180722-sagit-Official

twrp-3.2.2-2-sagit-shev.img

Magisk-uninstaller-20180719

Magisk 16.4

Magisk 16.0

Should I wipe dalvik,cache, data after install ?

I'm attached log from install Magisk:
[Magisk] Didgeridoohan:
[MENTION=6626572]_euphonic_[/MENTION] Can't see anything special in your logs, but what about Magisk v16.7?
[Magisk] handers1234:
[MENTION=4470081]topjohnwu[/MENTION] nvm
[Magisk] _euphonic_:
[MENTION=4667597]Didgeridoohan[/MENTION], firstly I will try Magisk 16.6 (Treble) :)
[Magisk] francyesco:
Hello, does magisk hide have something missing respect RootCloack (http://repo.xposed.info/module/com.devadvance.rootcloak2) Native detection lib?

Testing with RootBeer Sample, just enabling Magisk hide, native root sems to be correctly hidden, but using a specific function of my bank app (https://play.google.com/store/apps/details?id=com.latuabancaperandroid) will not work with just magisk hide enabled, i have to Use RootCloak, install "Native Root Detection" library, and blacklist the app, in this way root will be undetected by the app

Ps. i'm on LOS 15.1 so Android 8.1
[Magisk] jenslody:
Did you try to hide the MagiskManager by repackaging it with a random name ?

The option is in the settings.

In most cases that's enough, but you probably have to delete the data/cache of the app that has detected Magisk.
[Magisk] rakee:
Hey, guys.magisk can't boot on my Moto g6 plus(can boot on stock 8.0,but it cant boot on all gsi 8.1,bootloop), it have A/B partition.

I looked at the log file and it looks like the following is not happening during aosp startup:

07-29 12:13:55.298 715 1242 I Magisk : ** late_start service mode running

07-29 12:13:55.299 715 1242 I Magisk : * Running service.d scripts

07-29 12:13:55.299 715 1242 I Magisk : * Running module service scripts

07-29 12:14:20.351 715 739 I Magisk : proc_monitor: com.google.android.gms.unstable

07-29 12:15:46.017 715 739 I Magisk : proc_monitor: com.google.android.gms.unstable

How can i fix it?
[Magisk] amalvenugopal:
Anyone please help!!!

After flashing magisk I can't open clash of clans..

It stopps everytime.I tried clearing data , uninstalling and reinstalling etc..but in vain.Please help me.Iam on coustom rom 7.1.2
[Magisk] T.A.R.D.I.S.:
Hello

Do you try to hide your root for Clash of Clans with Magisk Hide?
[Magisk] Dims_Camper:
Fixed

Anyway, log attached

EDIT : it's fixed, my fault. My modules got conflicted so that's why.
[Magisk] amalvenugopal:
Yes.I tried but only after seeing that its not working.
[Magisk] ISoreo:
Clash of Clans not detect root try to uninstall Clash of Clans and reinstall again if FC try to Remove magisk and Flash Magisk again
[Magisk] francyesco:
yes and is not solving the issue, i've also disassembled the apk: is just checking for the su binary but magiskhide, i don't know why, is not enoght.
[Magisk] Didgeridoohan:
If there's something that can be improved upon, please post the information you have. Magisk log and a logcat when the app is detecting root, together with the apps root detection code. Those details would at least give anyone a chance to say what's going on...
[Magisk] DB126:
Well that's a crisis. Report certainly belongs in a beta thread. :rolleyes:

Wait - no logs? The mystery deepens.