yashsingh1/xdaforums huggingface dataset:
[Magisk] mofuson:
The result was the same.

Is it impossible to change /product partition?

crosshatch:/ # mount|grep product

/dev/block/dm-0 on /product type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)

crosshatch:/ # mount -o rw,remount /product

mount: '/dev/block/dm-0'->'/product': I/O error
[Magisk] kaibird:
UPDATE

Last time I tried flashing Magisk Canary Build v17.4-411ea56a I got stuck in bootloops

Now I am successfully rooted after flashing Magisk Canary v17.4-ceb51bb1 and no-verity-opt-encrypt-6.0.zip

I am screaming inside for joy, Finally!!!?
[Magisk] guest4711:
Perhaps you should use all the options given in the output of mount ... (e.g. seclabel,block_validity, user_xattr)

Or unmount it and then mount it again (umount -f /product)
[Magisk] bertino:
if anyone is still having trouble with banking apps even with Magisk hide enaveled for them, I have found a way to do it: putting the apps in shelter (a sandbox made for "big brother" apps. (May not be new, just thought I'd share what I found)
[Magisk] gloeyisk:
I found somewhere that someone already made a Magisk module for another root hiding options, the name is MagiskCloak module. I don't know if it's working or not. But so far I just stick with MagiskHide inbuilt from Magisk whether any bank apps for my country is working fine when I put them into Magisk hide. No root detection, and tested to any root checker.
[Magisk] cjrivera04:
Thanks for reporting. Sorry it didn't work.
[Magisk] beatschubser:
The official "DKB Banking" app can detect root as well, no matter what I try (Magisk hide, random package name, remove root permissions for all apps). Any ideas?
[Magisk] casouzaj:
I don't use this banking app, but I have installed it in my phone just to try to troubleshoot you issues. You know, just by checking its box in Magisk Hide list prior to its first launch, it seems to be working. My phone is a Sony Xperia Z3 Compact one, running CarbonROM 6.1 with the latest Magisk Canary build.
[Magisk] Didgeridoohan:
This has nothing to do with hiding root from an app...

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot
[Magisk] TonikJDK:
Often apps store the root check in their data, so after it is discovered you need to clear cache and data on that app and then hide root and then start the app. Based on the below I think trying that is a good bet.
[Magisk] beatschubser:
Thanks for testing the app, much appreciated. It does indeed work and shows your balance, but when you try to activate the "Verified by Visa"-feature, it tells you that the phone is rooted.

I have done this for each test, but without luck. I've never had issues with other Apps that use SafetyNet like RSA Token, but DKB Banking is giving me headaches.

Somebody in another forum mentioned it was necessary for DKB Banking to work, so I gave it a try. Didn't make much sense to me either.
[Magisk] detritu5:
[MENTION=4470081]topjohnwu[/MENTION] I think latest factory images for pixel 3 and 3 XL are not compatible with magisk

(november ota)

I can´t boot phone with magisk
[Magisk] drothenberger:
I am having the same problem with the Pixel 2 XL. The phone reboots back to recovery (TWRP in my case) when Magisk 17.3 is installed. I have not tried Canary.

EDIT: My problem was the Edge Sense Plus module. Magisk 17.3 worked fine for me after I disabled that module.
[Magisk] kost7:
Same issue for me, but the Canary worked just fine.
[Magisk] casouzaj:
Have you already tried to pinpoint any offending sub-processes which could be causing your issues? Through either adb shell or a terminal emulator app session, do this:

su
logcat | grep dkb

Then, by doing some analysis on its results, for each sub-process found, do:

magiskhide --add sub_process_found
[Magisk] thoughtfulwizard:
I'm also having the same boot issue with Magisk 17.3 on my Pixel 3 with the November update, but I couldn't get the canary build to work either. Is there something in particular you did to get it working?
[Magisk] kost7:
Not really, uninstalled 17.3, rebooted, went back to TWRP and installed Canary. All went well this time. BTW this is on a Pixel 2 XL.
[Magisk] drothenberger:
My problem was the Edge Sense Plus module. Magisk 17.3 worked fine for me after I disabled that module.[/QUOTE]
[Magisk] cjrivera04:
So I have a pixel 2 xl. I did an install of of the new November security update (I'm using latest twrp). I went back in and flashed 17.3 and then upgraded to the latest canary build 17.4.411 and now everything is back to normal as far as the charging issue is concerned. I'm also using a custom kernel, which I have been this whole time. I can't tell you if it was the Nov. update, the uninstalling of Magisk, or flashing from 17.3 to 17.4.411, but it's working now. Hope this helps someone with a pixel 2 xl.
[Magisk] drothenberger:
With 17.3 and the November update on Pixel 2 XL, plugging in the phone when it is powered down causes it to turn on and boot to system, which is new behavior.
[Magisk] martyfender:
Apparently it worked for you, the only thing I don't get is why you flashed 17.3 first, instead of just flashing the Canary build directly. That seems like to me an unnecessary, extra step. One big change from 17.3 to the latest Canary is that the Magisk database it now stored in the magisk.img and the code Fully migrated to C++.
[Magisk] Cares:
Try Canary build. No issues for me.
[Magisk] cjrivera04:
I agree totally. When I was flashing I wasn't aiming to fix anything. I had the 17.3 zip saved and not the canary zip (had done this zip through a direct install). So I flashed everything and get my things set up. Then charging issue went away. I just thought I would report on what I did the way I did it.
[Magisk] jackint:
If anyone is experiencing lag or stuttering after flashing magisk, try flashing an older version in TWRP and then update via magisk app after booting. This worked for me.
[Magisk] martyfender:
I didn't experience any significant lag after updating my unofficial build today, but Google Play Services updated today and I had longer than usual lag after the update, it took a much longer time than usual to settle down after the update. I am on the beta channel for Play Services.
[Magisk] SOCOM-HERO:
Strange, I tried this (although 17.1 was the only one I did via TWRP zip, 17.3 ) canary was done via direct install in app. None of that fixed it for me on my OP6. I reported the log after booting to canary in that thread. Hopefully something comes of it.
[Magisk] beatschubser:
Ok, I have the logcat output, but how do I identify the process-names? I see de.dkb.portalapp a lot, but that's just the package name I guess..
[Magisk] casouzaj:
Upload its contents to a post of yours. I'll try to help you out analysing it.
[Magisk] jtf420:
Device/ROM - Pixel 2/walleye-pq1a.181105.017.a1 (NOV Update)

Tried Magisk Stable, Beta and Canary Build v17.4-411ea56a - Phone reboots until original boot.img is reflashed.

Any advice!!
[Magisk] Strephon Alkhalikoi:
Does this happen with a custom kernel? Magisk works fine here on a Pixel 2 XL running the November update, so I believe the issue is with your device, not Magisk.
[Magisk] jtf420:
Not on custom kernel.

Thinking of a full wipe.
[Magisk] blazze11:
I can't install the magisk over the latest update on the pixel 3 xl (nov.2018)

I followed this guide which worked fine. Device boots and works normally.

Then I tried to install magisk again. First with v17.3 over twrp -> device boots into Android recovery "Cant load Android system. Your data may be corrupt..."

Reinstalled stock boot.img -> device boots.

pulled boot.img out of the factory image, patched it and tried to install patched_boot.img ->device boots into Android recovery "Cant load Android system. Your data may be corrupt..."

Reinstalled stock boot.img -> device boots.

Tried the same with v17.4. Same issue.

I could select "Factory data reset" in the Android Recovery menu but I don't know if this would work. I would like to keep my data. So I didn't try it.

Edit: Tried it again with the magisk_unistaller.zip and it works now, Weird
[Magisk] jtf420:
You ran magisk_uninstaller.zip from TWRP to clean device of previous magisk installation.

What process route did you take for reinstalling Magisk? Which version worked for you?
[Magisk] blazze11:
I booted up twrp with fastboot boot, flashed the magisk_uninstaller -> reboot -> boot twrp again -> install 17.4.zip -> reboot... Done
[Magisk] xunholyx:
Do you use Edge Sense Plus? If so, update the module for it.
[Magisk] kalawy:
at least we can have the option to choose if it is in downloads or another separate folder
[Magisk] Happy_Go_Lucky:
I tried opening the Jetstar (its an Australian Airline owned by Qantas) app and was greeted with "The Jestar app will only work on unrooted device"

I have ticked the check box for the app using "Magisk Hide" in Magisk however the app is clearly seen as being on a rooted device.

Any suggestions thanks.
[Magisk] gloeyisk:
Try to clearing the data? For these app?
[Magisk] Happy_Go_Lucky:
Thanks tried it but no luck. Still same issue.
[Magisk] gloeyisk:
Hopes this attached file help you :good:.
[Magisk] spawnlives:
Have just downloaded Jetstar app(from playstore) and tried it and does pick up phone is rooted.

As suggested hide in magisk hide ( don't have to hide manager ) force stop the app then clear cache and data. It's working for me .
[Magisk] Didgeridoohan:
Here's a list of tips on how to hide root from apps:

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

Tickle me pink and call me curious... Exactly what is that module supposed to do? It mounts an empty Magiskcloak.so file to /system/lib and /vendor/lib, but why?
[Magisk] gloeyisk:
It's simply my new experiment :silly:.
[Magisk] Didgeridoohan:
Ok... I gathered that much. But what do you mean to accomplish?
[Magisk] gloeyisk:
No no can we forget about this? I just try to help :fingers-crossed:.
[Magisk] HcoolP:
Hi,

i have an issue with my G950F (S8) with stockrom causing any version of magisk above 16.7 (meaning 17.1 17.2 17.3) to prevent any usage of the touch screens and getting non stop as if touch feedback (as i have feedback vibration on). i have tried uninstalling and reinstalling from TWRP and from manager and the only solution is to stick with below 17 version thus far.

any one had anything resembling that they were able to resolve in any other manner?
[Magisk] jtf420:
Yes. I do use the edge sense mod. But how to update it now within Magisk (as it's not activated yet), through flashing zip in recovery?

I uninstalled the app. But I think I the mod lives on. How to remove it?
[Magisk] Didgeridoohan:
Uhm... Sure, it's forgotten. But if you really want to forget about it, you should probably also edit the attached zip out of your post. With absolute certainty, there's going to be someone down the line that finds it and are going to wonder the same thing... :laugh:
[Magisk] gloeyisk:
It's ok I've removed the attached file :silly:.
[Magisk] exodius48:
Disable root & xposed. reboot. Then i get error CTS profile match : false

How to solve?
[Magisk] borelis:
Also got Note 4. Disable xposed in installer (if you have systemless xposed), reboot, toggle root off and start Pokemon Go. Sucess!
[Magisk] HtHNightwolf:
I finally got it to work on my bq Aquaris M4.5 and wrote a Step-by-Step guide here
[Magisk] allard1997:
Did you turn off root again after the reboot?
[Magisk] mlazzarotto91:
I don't know, I have the same error, but Pokémon is working fine [emoji2]

Inviato dal mio SM-N910F
[Magisk] JustFrame:
How do you disable systemless xposed? Should I uninstall it in the recovery?
[Magisk] Nandiacore:
open your xposed installer and disable the xposed status and then reboot.. you will pass safetynet check
[Magisk] topjohnwu:
Hmmmm.....

Seems mighty Google just updated the Safety Net detection for Xposed while I'm 100% working on the Magisk manager :D

Time for me to play with stuffs LOL
[Magisk] KaMyKaSii:
This means that there will be another delay for release v7? :(
[Magisk] borelis:
Toggle it
[Magisk] Norbix1999:
Magisk v6 not wroking Xpeira M4 Aqua E2303

After installation, I get a message that the su binary files are out of date

In Magisk I have a phone that is a non-rooted (switches are locked), and there is installed frameworks Xposed

How to fix it ?
[Magisk] Tha_Reaper:
If we would just be able to unmount/Mount systemless xposed on the fly without rebooting, that would be so awesome...
[Magisk] xstahsie:
I can now play Pokémon Go again after disabling Xposed. ?
[Magisk] diegonnc:
You guys probably care more about bug reports and usefull stuff , but i needed to post a simple thank you , such a wonderfull mod .
[Magisk] SidneyD:
/sbin/su is on a read only filesystem. In order to remove it, I must remount rootfs as read write.

That was the first thing I tried, and it did not work. It did not provide root.

On my first attempt when I used only phh-superuser-17-magisk.zip, Magisk never prompted for root access, and Titanium Backup failed to obtain root. Seems to me that phh-superuser-17-magisk.zip did not provide su binaries. When I used the base 'superuser.zip', root binaries were provided but Magisk Manager didn't work (the toggles are greyed out and unusable). Only when I use both the base superuser.zip and phh-superuser-17-magisk.zip do I get root and the ability to toggle it. However it creates /sbin/su and /data/su/ and since /sbin/su is on a read only filesystem I have to remount as rw to remove it. Otherwise my phone trips Safety Net.

This was the very first thing I did and it did not work. Since I believe I went through the process correctly, but since it still didn't work, I posted my step by step process in my original post.
[Magisk] Triviox:
Thanks for all !!! Now i cant login to play PoGo; we'll wait for update, anyway, was a great way to play PoGo :)
[Magisk] HtHNightwolf:
Sadly I cannot enter the game again o.O

What now?

Supertoll gesendet mit Tapatalk
[Magisk] stathis95194:
Guys just disable xposed, reboot and you are good to go until a more permanent solution
[Magisk] GatorsUF:
I already have Magisk installed with phh SuperUser, I'd like to give Xposed a try but the xposed instructions say to install the xposed.zip first then the magisk.zip. Do I need to fully unroot to add xposed or can I just install it on top of Magisk? I'm using the new AutoMagisk.

On an somewhat related question, does anyone know if android pay will work simply by taping the phone or must I open the AP app first to allow the AutoMagisk hide root?

Edit: I don't play PokemonGO so I'm not worried about that.
[Magisk] aliabkad:
safety net fails
[Magisk] thefireofwar:
OK I am not sure if this is the right place or not but here we go.

Today I wanted to use Google Pay and it told me that I am no longer able to use Google Pay contactless, so I checked Magisk for safety net and both are false.

I am currently on Magisk 17.3 Beta running RR unofficial for Mi Mix 2.

I have uploaded log file also the screenshot of the Magisk test.

Oh forgot to mention that I am on Android Oreo 8.1
[Magisk] D1stRU3T0R:
someone has an ideea how to fix Response PAyload validation failed ? I just uninstalled some stock apps, unsubscribedfrom google ads in settings and changed log buffer to none. And now I got this error :( I tested first, by changing log buffer and google ads first game me another error, reenabled, restarted, bug fixed. Now after I uninstalled some apps, it failed again. Help ?
[Magisk] Firestone_cz:
Hello and sorry for possible OT. I tried Magisk beta 17.3 with MagiskHide Props Config module for using Google Pay. It's possible that may be some problem with Magisk when I try to use Google Pay app and using as a contactless payment method? I've digitalized card and added into Google Pay application. But still I can't use paying via Google Pay. NFC is working and testing via sending files between devices.
[Magisk] Happy_Go_Lucky:
I cannot update Oreo on my S7. Reading various blogs it appears that the Knox is tripped when rooting the device and the trip causes the phone to be classified as "modified" when it checks for system updates. This means I have a great rooted device that Magisk allows me to use G Pay etc but that I cannot get system updates.

Is it possible to use Magisk Hide to hide root when the system check for an update?
[Magisk] jtf420:
I booted TWRP to install the updated mod downloaded from Github. Both, latest and the last version failed with ERROR-1.

I used the Magisk uninstaller zip through TWRP to clean the previous installation.

Installed Magisk, went straight for the canary builds. Everything worked and Magisk Root was attained.

Now I don't know what helped, the failed updating of the Active Edge Sense mod or the magisk uninstall.:cool:
[Magisk] spawnlives:
Yes your Knox is tripped and no you will not get ota updates again. Magisk cannot hide a tripped Knox.

The only way to do updates is to do it manually.
[Magisk] dejello:
Magisk and compressed (in this case--lz4) dtb's:

Forgive me if I have missed this somewhere.

I cannot get Magisk (17.3, and tried 17.4 canary build) to handle verity correctly as the dtb image for the Moto G6 is compressed (lz4-max compression) and is causing a no-boot situation. The ',verify' pattern is not touched as a result of the compression. If I manually decompress the dtb image using AIK and repack the boot image with the dtb not compressed Magisk works properly (and wonderfully!). I can see "Loading dtbs from [extra]" in the recovery log however there is no other mention of the dtb/fstab before repacking the boot image. With the decompressed-dtb image in the boot image I can see references to removing ',verify' from the fstab in the dtb.

Is this something that can be looked into? It would be amazing to not need to keep up with a list of manually edited no-verity boot images as there are several variants of this phone. I'll have to come back to provide logs if they are needed.
[Magisk] gnam:
On my brand new OP6T I unlocked BL and flash Magisk 17.3 and then 17.1, with both versions when I power off the device and plug in the AC charger the phone correctly power on but it stucks on screen advicing of the unlocked BL and doesn't go to the battery charging screen.

Removing Magisk the device works correctly.

Please help.
[Magisk] PowerOfTwo:
deleted
[Magisk] hyborian:
I I have Magisk on different phones, all ok. I recently changed the ROM on my Asus phone to resurrection remix. All ok, except for one thing.

Sometimes, the root permission I have given to apps all disappear, and I can't figure out why at the moment. I then grant all these apps the permission again. A few days later, it would disappear again. Something is triggering it.

How can I prevent this ? Is there a file in magisk that I should lock so it won't get erased ?

Thanks
[Magisk] demonoidmaster:
no, clearing magiskmanager app data will delete ANY app data, including any apps asked for root, magiskhide listed apps, etc settings

---------- Post added at 11:32 AM ---------- Previous post was at 11:30 AM ----------

has nothing to do with magisk, post in the YouTube vanced module thread

---------- Post added at 11:34 AM ---------- Previous post was at 11:32 AM ----------

XDA Search is your friend.

---------- Post added at 11:46 AM ---------- Previous post was at 11:34 AM ----------

Then try vol up instead
[Magisk] jenslody:
No, root-rights are stored in a database and it survives, the same is for the hidelist, which was stored in a file and now (canary) also in a db, and the systemless hosts setting.
[Magisk] hyborian:
I tried clearing cache and data of Magisk Manager, root-rights did survive.
[Magisk] cash money42k:
In this new update modules are working but root isn't any solutions? My device - leeco le 1s (mediatek helio x20 soc)
[Magisk] jegavelan:
What did you do different I am facing the same issue I tried more than couple of installation and un-installtion but same issue.
[Magisk] serajr:
magiskpolicy

Edit... done!!
[Magisk] SOCOM-HERO:
Same issue has been reported numerous times, no fix as of yet.
[Magisk] crescentmage:
Any updates on support for Fate Grand Order? I haven't been able to play it on my OnePlus 6 since August, and I know that a number of other FGO players are also unable to play due to new detection methods. I've verified that it is definitely Magisk that is causing the issue; FGO runs just fine when Magisk is uninstalled. I've tried the latest canary builds, hidden FGO, and repackaged Magisk, but it still gives error 61 when I launch it. It seems like the 17.2 release fixed FGO for some, but not others.
[Magisk] martyfender:
A fix for this problem is included in the latest unofficial builds by [MENTION=3306843]kantjer[/MENTION] and [MENTION=7187684]ianmacd[/MENTION].

It should be also included in the most recent Canary build also, but is not listed in the changelogs of the recent 2 Canary builds, so I am not 100% certain.

https://github.com/topjohnwu/Magisk/commit/be5f00aa1abfaabdda00e4476748acda58346b97
[Magisk] lukikow:
After root phone with magisk 17.1 i can't send any files by messenger lite. I'm on xiaomi mi a1. Anyone can confirm it? Or maybe there is a known solution?
[Magisk] einholzstuhl:
I don't have any Issues, but I have Magisk 17.4 and Iam in the beta channel.

MiA1 Android 9 with Rom:Liquid Remix
[Magisk] Schmand:
Hey,

I have the problem that if I install Magisk and repack the App with a different name, the app will be duplicated after reboot. If I do not reboot, the app will start (Without hiding Magisk Manager self and only the app, not) One says that I have to install manager app, and the other stuck on splash screen.

I really need this feature for using an important app. Without the magisk manager hide function it will be dedected (Magisk Hide for app is active)

Using Honor 8x wit EMUI 8.2, Android 8.1 and Magisk v17.1 (stable)

Hope anyone have a solution.

[IMG="Screenshot"]https://push.schmandre.de/2018-11-09_11:39:08_542898fc9be8698134eb2479d347926e.png[/IMG]

Regards

Schmand

//UPDATE

Generated own thread.
[Magisk] demonoidmaster:
fine whatever, might work for you but for me last time i ever had to clear my magisk app data everything was gone, host, hide, root perms, etc, but i guess that might be because Topjohnwu made magisk store it's files elsewhere compared to before previously
[Magisk] jenslody:
The hidelist was always in the magisk.img and not deleted by clearing MagiskManagers data/cache, but is now in magisk.db (as far as I know, at least on canary builds).

Root access stuff is in magisk.db since a long time too. Systemless hosts is detected by checking for the hosts-file in the (mounted) magisk.img and is not stored in any settings, so it can not be cleared together with the other settings like theme, timeout when asking for root, update-channel etc.

Edit:

if root-acces information is gone after clearing data/cache it can be because of a corrupted and therefore newly created database file (normally not related to clearing data, but done after a reboot).
[Magisk] hyborian:
Oh, thanks ! I thought it was just something on my other phone, as it was ok on the others.

I now use the Canary Release channel on all my phones.
[Magisk] matthias@matthiasmarx.com:
Pixel 3, Nov Build.

Trying to install Magisk without success.

All steps were been done like this https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/

Pixel 3 is unlocked.

But every try to install Magisk, 17.3, 17.4-4cdd66ce have the same result. Smartphone always comes into a boot loop.

Has anyone ideas for solving this?

Thx

Matthias

---------- Post added at 10:09 AM ---------- Previous post was at 10:09 AM ----------

Pixel 3, Nov Build.

Trying to install Magisk without success.

All steps were been done like this https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/

Pixel 3 is unlocked.

But every try to install Magisk, 17.3, 17.4-4cdd66ce have the same result. Smartphone always comes into a boot loop.

Has anyone ideas for solving thing this?

Thx

Matthias