yashsingh1/xdaforums huggingface dataset:
[Magisk] icanttinkofaname:
[MENTION=4487388]jcmm11[/MENTION]

Thanks for pointing me in the right direction.

I've read through it and I understand that I need to use the TWRP terminal to disable force preserve encryption.

Disabling dm-verity and forced encryption

If you on the other hand want to disable either dm-verity or forced encryption, you can go about it the same way as described above. If you're using the .magisk file method, just change KEEPVERITY and/or KEEPFORCEENCRYPT in the commands to false:

echo KEEPVERITY=false>>/data/.magisk echo KEEPFORCEENCRYPT=false>>/data/.magisk

If you can't access /data (TWRP can't decrypt, etc) you can instead use either /cache/.magisk or/system/.magisk, but please note that using /system/.magisk isn't systemless.

The only thing I'm unsure of is the order of the process. I know the only way to remove encryption at all is format data, so that should come first I guess, then is it:

Format data in TWRP

Enter terminal and type

KEEPFORCEENCRYPT=false>>/data/.magisk

(can I just type this or does there need to be anything else? I already have latest magisk flashed as well as latest manager)

Reboot to system

???

Profit?
[Magisk] sambhav14:
Magisk hide not working for app madhaar
[Magisk] martyfender:
A search on the playstore brings up nothing for me in the US. You give us very little to go by. Take a look at this guide:

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

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] jcmm11:
One caveat - I'm running encrypted (see no reason not to) so have no practical experience with this. What I would do:

1) Flash stock (unrooted) kernel. You're going to lose all your mods and apps when you format data anyway.

2) Format data

3) enter terminal and type command. Nothing else needed.

4) dump the contents of the file I just created using a cat command to verify that it contains what I want - i.e.,

cat /data/.magisk

The result should be

KEEPFORCEENCRYPT=false

5) Flash Magisk

NOTE: you have to flash Magisk in order for it to read the KEEPFORCEENCRYPT value. If you had kept the already installed Magisk without reflashing you would have encrypted again. Flashing an unrooted kernel first also ensures that Magisk can create a backup of the kernel - otherwise it would have nothing to backup.

6) reboot to system

7) Profit!!!
[Magisk] Rinoceros:
Seems to be an Indian government application (link).
[Magisk] frakk_2000:
Hi, thanks for your post, it's great to know I am not the only one :)

I have a vague idea why this may not work as expected - I am not sure what is the source for the "Restore images" function, but as far as I remember when I rooted the phone originally, I have flashed the patched boot image to BOTH slots (A+B). Now my thinking is, what if "Restore images" will try to restore to the other slot (nopt sure which one of the two is active, but practically both have the same patched file), then the restore result is basically "restore" the same status (patched, rooted, etc.) again. ?!

If anybody could drop a light on it...
[Magisk] icanttinkofaname:
Perfect thanks. Now to go hunt down a stock kernel!
[Magisk] guhvanoh:
So now that you're on 19.0 what happens if you upgrade to 19.2?
[Magisk] jctmobz26:
Anyone noticed some abnormal battery consumption when updated to latest stable build and manager? Any workaround to fix this? I thought it's ROM issue so I dirty flashed but still the same. Thanks
[Magisk] Tommasoleone:
Hello, You have find one solution?

I have write many post but i dont receive answer. I have root samsung a7 2018, s8 and other device with android pie but after root unlock screen (pincode,pattern, ecc...) dont working.. i can configure but if insert correct pin code i see error for incorrect pin code..same issue with pattern..I have try with magisk 18, 18.1, 19 and 19.1..i have try no verity 6.0 and 1.0..but have lockscreen issue..have see many post with same issue..Have solution?
[Magisk] FoOlKeN:
No i didnt find any solution...and im searching always
[Magisk] wilsonhlacerda:
Have you used something like app BetterBatteryStats to confirm that? Have you disabled modules (core only mode) to confirm it's not a module that also was updated?

By the way, I myself not having any weird battery consumption after upgrade. (LOS14.1)
[Magisk] AndrzejDwo:
And did you guys tried to report your issues properly? If you didn't provide logs then your problem doesn't exist.
[Magisk] FoOlKeN:
Logs...how can i have logs because i can root my device but the problem is in SECURITY settings
[Magisk] AndrzejDwo:
So? You think that there are no logs than? That's interesting... Force this problem, collect logs and post them here. I'm sure that someone here (wiser than me) will be able to help or advise you.
[Magisk] strikerz911:
On 19.2 after reboot I cannot get back into my phone (Oneplus 5T using stock rom Oxygen OS). After the bootup logo, the screen goes blank. The only way to solve this was to downgrade to 19.0 using TWRP recovery. I got this from the Magisk github page.
[Magisk] mspasov:
Same here with the latest Canary debug, N5x, pie. The problem is actually with MM 7.2 debug. I flashed previous version of magisk.zip -battery in Settings still reports Turn battery saver on the moment I unplug the charger. Uninstalled Magisk Manager 7.2 - everything is back to normal
[Magisk] hachamacha:
I've got close to the same situation but on a oneplus 5 (OOS & TWRP), identical symptom. I'd been running 19.1 Magisk since it was out without any problems, so I reverted back to 19.1 after booting into TWRP. It's back to working fine. I'm sure I kept a log-file since I always do and will give a look for it. I see some commits pending in github so will try again after 19.2. Cheers.
[Magisk] wodgey:
thanks, this worked but needed to remove the PKG letters from the command you suggested
[Magisk] guest4711:
Thanks for reporting...
[Magisk] walkwitmeinhel:
Anyone here with emui 9.1 have issue with stuck at booting now screen ?
[Magisk] kotuamoalt:
Running 19.3 on Lineage 16. All is good.
[Magisk] Bi0haZarD:
19.3?? Back to the future!!
[Magisk] jcmm11:
19.3 is the latest Canary release. Currently it's the same as stable 19.2
[Magisk] Bi0haZarD:
Ok, thanks for the heads up! :good: I'm not using development builds yet, just stable ;)
[Magisk] kotuamoalt:
Hey, somebody's got to be the test monkey for this stuff...
[Magisk] InfX:
Still getting "not installed" on 19.2 stable, jist like 19.1, on my SGS7. Dirty downgrade to 18.1 works.
[Magisk] dermann:
Dirty downgrade, How? 18.1 zip via twrp?
[Magisk] InfX:
Yep
[Magisk] Tommasoleone:
Sorry but how can I get logs? root working and magisk working...but after root with magisk, lockscreen dont working..i have read many post in this forum of users with this issue.

I have try with all versions of magisk and dmverity..i have tested many device a7 2018, a6, a6+ (all samsung device with Android 9) only 1 device working: Samsung S9 but i have rooted with Dr.Ketan Fix .

But has anyone rooted a Samsung device with Android 9.0 that tried to set up a lockscreen and verified that it works? (Rooted with twrp, dmverity and magisk)

Thanks
[Magisk] damadikaz:
Hey.. anyone having problem with edXposed?

Riru core is okay, but when I enable Riru edXposed some magisk module become weird, YT vanced reset to default settings (theme changed to white, and shows welcome dialog every reboot), viper4andrid behave about the same, shows welcome dialog and asks storage permission after every reboot. Other than that they work fine. This problem is gone when I disable riru edXposed. I've clean flashed my ROM, start fresh still no luck. Been trying to troubleshoot myself for about a week now, haven't found any solution yet.

Basic info: LG H990DS, LOS 16, magisk 19.2, magisk manager 7.2.0.

By the way I use xposed to disable full screen keyboard on landscape with gboard and to lower my screen brightness. So anyone knoe magisk module that do this job?

Edit 1: I can only reproduce this bug in my LG H990DS, my other device works just fine with edXposed. I think it's ROM bugs but anyone have an idea what cause this issue?
[Magisk] AndrzejDwo:
This is how:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] Didgeridoohan:
Been reported quite a few times actually... EdXposed seems to break the Magisk boot process on some devices. The late_start service mode runs too early (or magic mounting happens too late, not entirely sure which). It needs to be brought up with the EdXposed developer, not here.
[Magisk] damadikaz:
Thankyou very much for the answer, now I know why. So sorry for not digging deeper into this thread first.

But how could it be happening on certain number of magisk installation only?
[Magisk] darfri:
Edxposed is still raw. Makes your device slooow. It needs to grow up so I am waiting for bigger updates
[Magisk] Tommasoleone:
Thanks, but i think i cant get logs because magisk working...but cause lockscreen issue. I think all samung device with Pie have this issue, only solution its understand why dr.ketan fix working.
[Magisk] mulecumu:
uninstall Magisk without custom recovery

Hey,

hopefully somebody can help me.

I'm stuck in a bootloop after updating magisk modules. Unfortunately I don't have a custom recovery.

Is there any other way to use the uninstall zip or to delete magisk with the modules?

I can still use my phone if I boot from the unpatched boot.img but it would be nice to have root again.
[Magisk] mrps2:
Redmi Note 5 - MIUI 10.1 - Still having bootloop when accepting to do Additional Settings... If I don't accept it it does not allow me to install any module. 19.2 Magisk keeps asking for install additional settings...
[Magisk] AndrzejDwo:
What do you mean with "lockscreen issue"? I'm on S8 PIE.
[Magisk] alagga:
Just wanted to tell, that the new Magisk Manager update 7.2.0 (213) is so ugly with Dark Mode enabled.

Before it was a smooth Material Dark, now we got material dark on complete black in the module overview and complete black in the dashboard.

Also the cards in the module view take too much space in my opinion.

Before the update it was much smoother.
[Magisk] xunholyx:
If you feel this way, you're going to be really disappointed with Android Q's dark mode. I suggest you get used to it.
[Magisk] cnjax:
Looks fine on my LG V20
[Magisk] elwhiteboy01:
Yeah I updated and the manager keeps closing upon opening the app. Had to uninstall and downgrade to an older version off apk mirror.
[Magisk] Tommasoleone:
After root with magisk manager and setting one lockscreen (pincode, pattern, fingerprint, ecc...) screen won’t unlock and PIN not working. Example i have setting one pincode for unloock screen, have entered the correct PIN code but it’s still not working (Wrong pin code) and i cant unlock screen. I have same read many post for this issue ( example [RECOVERY] [ROOT] TWRP 3.2.3-1 Galaxy A6 + / A605).. I have try with A6+, A7 2018 and another phone (all samsung device). Only S9 with Dr.ketan Fix lockscreen working after root. You can try to setting one lockscreen after root?
[Magisk] AndrzejDwo:
I have pattern unlock set without any issues. To be honest I have never heard of that issue. You can collect logs through ADB, connect with the computer and check always allow (adb debugging), flash Magisk with twrp, collect logs while your issue appears.
[Magisk] Tommasoleone:
You have flash twrp==>flash RMM-State_Bypass_Mesa_v2.zip==>flash no verity 6.0==>flash magisk. Its all right?
[Magisk] m i n a r:
last time i updated from 18.1 to 19.1 i had to wipe my data to make the phone boot. Today i tried updating to 19.2 and again, bootloop and no way to recover (uninstaller does nothing, 18.1 does nothing). This is the last time i try to update (and we're talking of a "stable" version) [MENTION=4470081]topjohnwu[/MENTION], you definitely need to add a safe upgrade system. I agree that i have an old device (Oneplus One) but a stable version should at least boot on every supported device.
[Magisk] AndrzejDwo:
Yes, maybe with earlier version of no_verity. It was a long time ago... It's all right, and it was from the beginning... You have all the instructions and downloads in TWRP thread.
[Magisk] yasxc:
Never change a running system. I do not upgrade anymore, if I don't have a explicit reason for, like banking apps not working anymore etc. Stay on the older version if your root works. No need to upgrade.
[Magisk] guest4711:
And how he should check it if nobody complains on beta/canary versions about such a problem with his device? Without logs and proper reports there's no chance to check and probably fix.

You are not talking to a big company with lots of employees and devices - you are talking to an one man show who does everything for free.
[Magisk] InfX:
TBH, i've been thinking a "stable" branch means well tested, with no major issues such as bootloops, "not installed" etc. With others, ones on the beta branches, experiencing all this and devs weeding it all out. Apparently, not so much, at least according to my own experience with the last 2 stable versions and after reading the tail of this thread.
[Magisk] TGN:
Amen to that.
[Magisk] newkydawg:
Yes. Go to Modules in Magisk Manager and click the yellow plus sign as if to add a module. Navigate to where the uninstaller zip is located and select it. I accidentally did this earlier today. LOL
[Magisk] Bi0haZarD:
Just delete the modules from the module folder ;)

Edit: They're located under /data/adb/modules
[Magisk] m i n a r:
I know and I'm not complaining, it was my fault, considering there was no point in upgrading (everything was perfect on 18.1). I simply gave an advice: magisk prompts each user to upgrade without mentioning the possible issues. And 2 times out of 2 it killed my One. I'll think twice before updating next time.
[Magisk] anykiel91:
Has anybody ran into issues on nonbooting oneplus 3t on stable Pie release?

I'm having an issue right after installing Magisk and the only way to boot is to run Magisk uninstaller. More info here :

https://xdaforums.com/oneplus-3t/help/magisk-install-pie-t3933760
[Magisk] schlubbi:
also bootloop here on Mi8 UD.

Problem is, i get the loop on all versions of magisk.

I use:

Rom: global dev 9.5.17

twrp: 3.2.3-1208 Firedance-Edition

tried magisk 16 up to 19.2

tried to flash stock boot from fastboot rom

still loops

installing uninstaller ends up in error 1
[Magisk] stab244:
I seem to be having an issue with getting magiskhide to work properly with an app called Island. What the app does is create alternative copies of apps so you can run the same app twice. With Pokemon go it works on the main copy. But the copy of it keeps detecting root at some point. Should I make an alternative copy of Magisk Manager to run in that profile for the copy of pokemon go? This didn't happen until Magisk 19.2.
[Magisk] JudgeDread11:
Do you have multiuser seeing on in Magisk? If so turn it off and try again. If you need root within the island then you will be to make an island copy of Magisk manager as well.

I don't use root on island and don't play Pokemon so other then this I can't give any advice, sorry.
[Magisk] Tommasoleone:
Hi friends, i have try with A7 2018 and A6+ with Android 9 and i have try with No verity 6.0 and Universal No Verity. I have see post for root of Samsung S8 with Android Pie but you have used Pie G955F Root for OEM issue by Dr.Ketan? Because i wrote that Samsung S9 with Dr.Ketan fix working very well and dont have unlockscreen issue.

Have lockscreen issue with only device rooted without Dr.Ketan Fix!
[Magisk] martyfender:
You post this Dr.Ketan thing assuming that most of us know what it is. Please clarify what this fix is? Most of us don't have your device to know what it is?
[Magisk] Tommasoleone:
Hi, i have explain issue but repeat no problem. I have rooted A7 2018 and A6+ with Android Pie and after root have unloock screen issue, if visit post of this device you can see other people have this issue.

After root with magisk manager and setting one lockscreen (pincode, pattern, fingerprint, ecc...) screen won’t unlock and PIN not working. Example i have setting one pincode for unloock screen, have entered the correct PIN code but it’s still not working (Wrong pin code) and i cant unlock screen.

I have try all versions of Magisk, No verity 6.0, 1.0 and Universal No verity and have try to change firmware.

After test have try rooted one Samsung S9 with Dr.Ketan Fix (OEM Patch + Root method in aroma) you can see post of root samsung s9 xda. With this method dont have lockscreen issue.

AndrzejDwo have rooted Samsung S8 and dont have lockscreen issue but this device using Root method by dr.ketan fix.

Dr.ketan root its automatic root method with setup in aroma. You can see details in the post of root s8 or s9 by dr.ketan.
[Magisk] martyfender:
Again, I would suggest you try to get logs of this issue, you should be able to find many way to do this with this guide:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] mulecumu:
Thanks for replying first of all.

I can either boot from the patched boot.img, then i have root but bootloops. That way i can't use root.

Or i can boot from the original boot.img, but then i don't have root and no way to add a module or delete the modules manually.
[Magisk] hfam:
I know zero about the Samsung or dr.ketan, but why not just flash a clean boot.img from your current OS installation package to remove Magisk and see if your pin comes back? Then you can reroot with Dr ketan and at least you'll be back into your device and Magisk will no longer be in play. You can then put the security back in place (or not, your choice) and decide how to proceed from there regarding Magisk, maybe try it again with no pin in place so as to avoid and get past this issue.

To be perfectly honest, I remove my screen security before I update Magisk every time. Pixel 2 on Pie here, but I had a weird similar thing happen a few major releases back with Magisk in conjunction with some bootlooping and it's just part of my routine now.

It may be overkill/overcautious on my part but it's one less thing to worry about when updating to a new Magisk release and it's dead simple to add to my update routine.

Anyhow, hope I was some help. Good luck to you.
[Magisk] Tommasoleone:
Hi, i have flash stock firmware. My issue its if rooting i cant set pincode or pattern.

Dont have update magisk and dont have pincode before root, samsung a7 2018 and a6 its New Phone with stock firmware. I cant rooting with dr.ketan because this Root method its only for samsung s8 or samsung s9. I have root many device with many version of android. This issue have only with Android Pie.
[Magisk] AndrzejDwo:
[MENTION=9904126]Tommasoleone[/MENTION] I still don't understand your problem. As I read in Dr.Ketans thread, the problem was existing when there was no possibility to decrypt /data with TWRP (I remember using modified TWRP, tho) and now, since we have 100% working TWRP you should only follow the instructions for your device.

Here is an advice from Corsicanu and HadesRom thread:

"If you get pin locked after flashing go to findmymobile.samsung.com and try one of the following:

- lock your device and set a pin which you'll use to unlock after that from the phone

- reset all the locktypes, pin, password, patter

If you still can't unlock with the above method, restore backup of previous rom, log out from samsung account and then flash back v6"

I think we've already bloated this thread enough... If you still have problems, search on your device forums threads.

Cheers

Edit: I'm not sure if it's your device, but take a look here:

https://xdaforums.com/samsung-a-series-2017/how-to/guide-root-install-twrp-samsung-t3747535

https://xdaforums.com/samsung-a-ser...m-hadesrom-pie-stock-v1-0-a5-a7-2017-t3926709
[Magisk] hfam:
Ah. Well, [MENTION=8126387]martyfender[/MENTION] was plenty of steps ahead of me then when he recommended getting logs. Sounds like a complicated issue.

Good luck.
[Magisk] AndrzejDwo:
https://xdaforums.com/galaxy-s8/sam...ment/fix-data-mount-fix-s8-twrp-oreo-t3769254

I don't think it's necessary anymore... Personally never used it...
[Magisk] guest4711:
Have you tried to create /cache/.disable_magisk via ADB to force core-only mode of magisk?

Or to fastboot TWRP (without installing it) and to disable/delete the failed module from /data/adb/modules?
[Magisk] Tommasoleone:
Sorry if have "bloated" this thread..if you search you can find many thread (root A6 and A7 2018 with this issue and zero solution. Example [MENTION=9829413]FoOlKeN[/MENTION] have same issue. Thanks anyway
[Magisk] koko115:
Hi. I have problem with magisk and my tablet Galaxy Note 12.2 LTE android 5.02

After install Magisk 19.2 and reboot keyboard samsung crash without any crash log.

After unninstall magisk keyboard works good.

I wipe this tablet, and after install magisk problem still exist.

How fix this ?
[Magisk] guest4711:
Install another keyboard, e. g. AnySoftKeyboard (Alternative keyboard) - https://f-droid.org/app/com.menny.android.anysoftkeyboard

Without logs none could analyze the issue..
[Magisk] koko115:
For s-pen oryginal keyboard must be.
[Magisk] guest4711:
Did you try to hide Magisk to your keyboard (add to s-pen)?
[Magisk] Verequies:
How does one get 'adb root' with Magisk Hide enabled?

When I try to run it, I get 'adbd cannot run as root in production builds'. Turning off Magisk Hide allows this to work.
[Magisk] koko115:
How add app to magisk hide in latest magisk manager ? I dont see this option. See screen shots

https://zapodaj.net/ac7e09efff40a.jpg.html

https://zapodaj.net/ed2eb57916e8f.jpg.html
[Magisk] martyfender:
Go to Magisk Manager settings, turn on Magisk Hide, then kill and restart the app. The app must be relaunched for the setting to take effect. I get that same screen if Magisk Hide is turned off in settings. If that does not work then something else is going on.
[Magisk] jcmm11:
What happens if instead of "adb root" you run normal adb then enter the su command?
[Magisk] Verequies:
That works, yeah. Is there a way to restart adbd as root without 'adb root'?
[Magisk] Didgeridoohan:
If you really need to use adb root, and don't want to turn off MagiskHide, you can use the MagiskHide Props Config module to reset ro.build.type and ro.debuggable to their original values (the "Edit MagiskHide props" option).
[Magisk] ashish1989:
Have magisk installed v19.1 with miui 10.3.1 stock rooted mi note 5 pro

Banking apps like PNB mPassbook and syndicate passbook, google play not working

Everytime your phone is rooted is coming tried with magisk hide but of no use
[Magisk] Didgeridoohan:
I'm going to assume you mean this app:

https://play.google.com/store/apps/details?id=com.mobile.syndicatepassbook

If so, I tested and there was no issue hiding root from it, suggesting that it's an issue with your setup rather than MagiskHide.

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] martyfender:
In addition to hiding the apps, did you delete the apps data and cache?
[Magisk] guest4711:
Couldn't have said it better...
[Magisk] Momotani-Hitoshi:
Installed 19.2 on my Pixel 3XL and Cerberus is spamming for root permissions when google maps directions is open. Magisk logs is filled with request and toast msg is perma on the screen.
[Magisk] dnfm:
The latest version of magiskmanager is broken.

It doesn't offer the preserve avb/dm-verify option anymore, and older versions refuse to install without updating magiskmanager first, so devices that require that option can no longer be rooted with magisk.
[Magisk] mulecumu:
If i try to push it, i get Permission denied.

Unfortunately there is no TWRP available for my phone.
[Magisk] JudgeDread11:
I think it's something on your phone that breaks it. No problems with those options on my phone.

To downgrade, flash the uninstaller and then flash the Magisk version you want.

To get help for your problem, provide logs.
[Magisk] dnfm:
This is on an nvidia shield TV, which cannot just be 'flashed', but requires a patched boot.img.

And the magisk user interface on android tv looks *nothing* like that and provides very few options (and the UI is broken on TV too, since you can't click install without connecting a mouse, as there's no way to highlight the install button.)