yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
By default, when you flash Magisk it disables encryption unless your data partition is already encrypted. On my devices I had to either delete the userdata partition, or factory reset, then flash Magisk, all before a reboot, so that upon reboot, a new, fresh, unencrypted data partition could be created. You may also need to flash a stock boot.img before flashing Magisk, also.

If your data partition is encrypted, flashing Magisk will not magically unencrypt your data.

When you do the above, the first boot will take some extra time, as the new, unencrypted data partition is created. On my devices, this first boot can take up to 5-7 minutes and the device will appear to be bootlooping on the animation screen, but will eventually will boot to the Android setup screen.

This is on my Nextbook Ares 8A tablets which are not type A/B devices and have separate boot and recovery partitions.

Possibly better info concerning your device can be found on your devices forums. I don't believe you gave that device and Android info.

The above advice is based on my devices and experiences and could potentially be much different for your device.

---------- Post added at 03:26 AM ---------- Previous post was at 03:15 AM ----------

I don't believe the above will unencrypted an already encrypted data partition, though. I could be wrong?
[Magisk] Artim_96:
Well, guess why wrote that this only disables force encryption. So when you remove the encryption it makes sure Magisk forces the device to keep it that way. Don't know if the same happens when you just format data and then flash Magisk, but this one makes sure Magisk will do it
[Magisk] Valfaun:
Updated from 18.3 (I think) to 19.1 via the Magisk Manager updater earlier, like I did a couple times before, and now my device won't boot anymore. Recovery also prompts me with a data decryption password now, which I don't have. So... I guess I'm screwed now?

Using a OnePlus 5T running (the discontinued) ZoeRom and bluspark kernel
[Magisk] Xdevillived666:
Thanks. I did. I see it said it supports q beta 2. Wasn't sure if that's specifying anything new outside of the pixel 1 and 2 that were already supported.
[Magisk] pac213:
What if I flash a new vendor firmware?

EDIT: Pocophone F1 using LOS 16.
[Magisk] drezz2:
What I can do? Can I uninstall the manager and magisk and go back to the previous version?

How do I do it with magisk?
[Magisk] xNoFantasy:
Tried to flashing the new version 19.1. Tried with direct install and flash from recovery but in both cases, when I boot it asks me to format data for problem regarding encryption/decryption.

Returned to 18.1 and it's going well.

Huawei p9 lite, rom stock with magisk, some modules and twrp.

Any solution so far?
[Magisk] Ksawery:
I've the same problem with my Huawei P9 Lite!
[Magisk] Klusio19:
I can't even say if 19.1 is buggy because it fails to flash in TWRP. "ZIP file is corrupt!"

Any help?
[Magisk] AndrzejDwo:
Try to download it once again.
[Magisk] NoxOn3:
Hey there, I've updated to v19.1 and my camera stopped working. Always force closure. Yet I can't an versions beyond to work... It always says magisk not installed... What to do?
[Magisk] levone1:
Uninstaller worked to revert to working 18.1. Then, I wanted to mess around more, to see if I could get new version working, and after a few flash/bootloop/downgrade-type attempts, I ended up with, "your device is corrupt and cannot boot". So re-flashing stock now... Seems like v19 is not quite ready...
[Magisk] Tianhe:
Contrary to most of the reports here, I am lucky that the update to v19.1 went off smoothly. Updated Magisk Manager and subsequently Magisk directly from v18.0 to 19.1 with recommnded (direct install method). No bootloops or force close and normal reboot time.

Device: Asus X00TD (601KL 6GB Variant) with stock rooted Oreo.
[Magisk] kewinhw:
Updated from beta 19 to 19.1 through magisk manager without problems
[Magisk] xNoFantasy:
Do you have any particular config/rom?
[Magisk] drezz2:
if i install the previous manager and the last magisk.. crash?

Due to the problem I have with the cerberus requests I have put the previous manager with the last magisk and now the manager continuously gives me error (stopped responding)

i uninstall manager but everytime i reboot.. the manager still in the app box, why?
[Magisk] gedod:
Me too 19 to 19.1 (via twrp for me) and 7.1.1 to 7.1.2 on an Xperia X, all updated no probs. Thank you very much
[Magisk] daddylonglegs:
Yep I uninstalled and reinstalled it. It's still detecting root. It's insane because literally every other app cannot detect root. Only the Nintendo Online app. Could it be detecting Busybox?
[Magisk] akxak:
Maybe.... I use plain Magisk 19.1.
[Magisk] daddylonglegs:
Yep. It didn't help.

Is it possible it's detecting Busybox? It's incredible that this is the only app detecting root. Even my banking apps don't. Nintendo is insane
[Magisk] smart123123:
Same thing happened with me... So i tried to uninstall magisk from twrp using magiskunimstaller.zip and rebooted.... But dont know why ... My /system wiped out... So i flashed again with sp flash tool... And then again installed 18.1
[Magisk] k1ll3r8e:
P9 Lite Magisk 19.1 = Dead Phone

-

After installing the lastest version via the Magisk App the restart ends in an encryption bug... The password should be fine but the data is destroyed... Also, the backup from the previews version was deleted, so no "easy" rollback possible. - Seems Magisk 18.1 is working fine.
[Magisk] solbakk:
Hi! Is there any way of not tripping banking apps and so on with magisk? I had magisk but i unrooted since daily use my bank app.

[samsung s8]

Thanks!
[Magisk] Ksawery:
No. I've a stock rom. I've Xposed for Magisk installed and some modules also.
[Magisk] xNoFantasy:
Me too. Luckily reinstalling 18.1 via twrp everything seems fine
[Magisk] pkn267:
This time I uninstalled v19.1 using the magisk uninstaller and after that I again flashed v 19.1 of magisk . Now it is passing safetyNet.
[Magisk] g000n:
Don't bother installing anything other than 18.1 on galaxy note 5
[Magisk] kost7:
No problems whatsoever updating from 19 to 19.1 in 4 different devices ( Pixel 2 XL, Nexus 6p, Samsung S9 & Moto G5+). :good:
[Magisk] nacos:
The new release definitely has a backward compatibility problem with older devices. 18.1 was working just fine on my Samsung S8 (Android N) while 19.1 causes all sorts of weird problems.
[Magisk] Einheit-101:
I updated the new Magist + xPosed framework module on my Phone. I got a bootloop. How to fix? I have no TWRP because no one is interested in ROG Phone.

€DIT: I simply flashed the patched_boot.img and the phone boots again... "Dont play on patch day" applies to Magisk aswell....
[Magisk] bafforosso:
Yes there are multiple solutions baked into Magisk to hide it from the apps that are checking for root access. Check that extensive guide by [MENTION=4667597]Didgeridoohan[/MENTION], you should find all you need : https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] Herox:
Can someone explain the Samsung AP part? What is it's use? Updating my watch plugin still causes detection of root in Spay (S watch) so I am curious if this can help fix that.
[Magisk] geckor:
Update from 18.1 to 19.1 was flawless on Xperia Z1 compact with AICP 14 and TWRP 3.2.3. I should note that the initial installation of 18.1 some months ago was not possible on direct way for Android Pie (always error in the Magisk Manger: "Not installed"). Therfore I had to modify the boot.img and flash it via fastboot. But the update to 19.1 worked without any problems. Thanks!
[Magisk] plusminus_:
Just in case this affects anyone else: simple mount has been removed (I think this is the relevant commit) so I copied the files from /magisk_simple/ into the folder for the systemless hosts module since it's pretty much static, and this is working as expected.
[Magisk] Son-j:
Yes make it the last one. I don't know why.

My theory is that while PHH SuperSU is highly compatible with magisk6, it makes the root status persistent and that's why the toggles doñt work.

The unSu somehow removes that persistence. So for now, I will use this process until PHH SuperSU gets updated . :)
[Magisk] Krunk_Kracker:
Running the unsu doesn't remove supersu?

---------- Post added at 09:37 PM ---------- Previous post was at 09:31 PM ----------

Well, I just tried it with your suggested order, and still the same thing. Maybe I'll hit up the Pure Nexus thread and see if anyone is using it there.

Also, I'm using the UPDATEunsu.zip by osmosis, if that matters.
[Magisk] Son-j:
Surprisingly no. At the point of flashing unSu, your system can now toggle between root or unroot status. I use cpu-z app to check on the fly.

BTW, we are referring to PHH-supersu (works well with magisk6) and not chainfire SuperSU OK?
[Magisk] JudgeDread11:
unSU removed SuperSU files from the system. It leaves the systemless location untouched.

It shouldn't matter in which order you flash it as long as magisk gets flashed before any modules (superuser, xposed, others).

Try uninstalling magisk and use root verifier to see if there are any traces of root left. If so remove them manually in twrp file manager.

Edit: also BusyBox should be removed.
[Magisk] got2best:
Answered somewhere earlier in the thread but this is a known ¿problem? .. issue? ... Basically AP only systematically checks for root. Unfortunately that means after you have disabled root you have to open AP select add a card as soon as it shows the camera back out and AP should work. This forces AP to check for root again then it will pass
[Magisk] Rls4ever12:
Need some help with arise just can't get it to work I have tried for 2 days
[Magisk] gk1984:
Set SELinux to permissive - works for me doing that.
[Magisk] Rls4ever12:
After setting seed Linux to permissive I still get the allow driver to automatically install message. I have Seen a couple of post about moving files? Thanks for the help by the way. I might pm u so I don't trash up the thread.
[Magisk] micksh:
Yes, I had Sony drivers from Sony PC Companion, they stopped working.

PC (Windows 7) showed phone as S1 service device with no drivers. I downloaded Flashtool from here https://github.com/Androxyde/Flashtool, installed drivers, now PC sees it as SOMC Flash device.

When I connect phone to PC LED light blinks red, then green once, then everything is black. And, neither fastboot nor adb see it.

I asked Sony Z3C forum, no replies so far.

UPDATE:

Please disregard this. I installed flashtool propery from flashtool.net and it was able to flash stock firmware. Also it looks like battery was fully drained, not sure how.

Now the phone is working. I lost root, but it's OK.
[Magisk] gk1984:
You probably have old Viper drivers somewhere on the phone. They won't properly overwrite themselves. Wipe system and reflash your rom.
[Magisk] ruifung:
Is there a updated version of phh's superuser for magisk? The current version appears to have issues with substratum in enforcing mode.
[Magisk] Gunbit:
Is there a way to install dolby app with magisk? Or we are stuck with the systemless v4a that was created?
[Magisk] alllle:
update to superuser binary

Same question here.

Getting prompt saying the the su binary is out of date. But I don't know if I can use the latest version here: "superuser.phh.me" (link), also not sure which version I should download from there.

Magisk works great, love it! Donated, please keep up the good work! Thanks!
[Magisk] borntobehappy:
It was OK but Magisk doesn't work (boot OK but I can't unroot . Target came back to "root"). I did a Back up so I restored.
[Magisk] ataraxist:
should there be a compiled list as to which device/rom work with magisk? i hope there is one soon...
[Magisk] supergrobi94:
It seems that the magisk method don't work with latest version 0.39.0 of pokémon go. The previous version worked fine with magisk. Is there someone else who can confirm this?

Gesendet mit Tapatalk für Android
[Magisk] toshi127k:
report of test result

First of all,excuse my bad english. I'm very sorry.

device Xperia Z1compact(D5503) BL unlocked

ROM SONY stock Android5.1.1(14.6.A.1.236)

as it is already known. boot image is broken if install magiskV6.zip on my device

I edit update-binary

Disable statement relating to unpack boot.img , repack boot.img and flash boot.img

ramdisk.gz from /data/temp.edit gunzip's standerd input

newramdisk.gz to /data/temp.edit gzip's standerd output

on device

flash stock rom

on PC(ubuntu etc)

unpack Kernel.sin

ramdisk put to /data/temp/ramdisk.gz

on device

reboot into TWRP

install (moded)magiskV6.zip

on PC

get newramdisk.gz from /data/temp

make boot.img

reboot device into bootloader

flash boot.img

on device

reboot into TWRP

install phh-superuser-17-magisk.zip and xposed-v86.5-sdk22-topjohnwu.zip

reboot into system

install magisk manager.phh's superuser and xposed installer

every thing worked for me

thanks awesome work

and excuse my bad english,again
[Magisk] Didgeridoohan:
Wrong thread...
[Magisk] Krunk_Kracker:
Yep, phh supersu, the flashable zip, and the apk.

No busy box huh? I'll remove it and see.
[Magisk] ykjae:
Question : How do I install Magisk on s7 edge? I am currently on a custom rom with supersu 2.78 installed. I unrooted with the su app then flashed Magisk and phh and ended up in a bootloop
[Magisk] ninken84:
Hi, im a xiaomi redmi 5 plus user.

rom PE Caf 9.0,

im facing rebooting prob afer installed 19.1

always rebooting after i clicked YES on 'required additional setup'

sorry for my bad english, provide ss and logs.

thanks
[Magisk] HpNoTiQ:
Hi,

I've tried to use magisk 19+ on my Samsung Galaxy A5 2017 running pixel experience since first beta/canary build but I always get bootloops to samsung logos.

I've tried to install it via magisk or twrp, tried after full uninstall but it always end in bootloop.

I need to flash back magisk v19 and it is working fine.

I can provide logs if needed.
[Magisk] Gold_Phenix:
Don't forget to flash again kernel if you uninstall or install magisk.

Wysłane z mojego LG-H850 przy użyciu Tapatalka
[Magisk] sinthemau:
Same behaviour here...this time all OK frrom 18.1 to 19.1 and 7.1.1 to 7.1.2 on Xiaomi MI A2 Lite on Pie.

Thanks to developer
[Magisk] drezz2:
i return to previuos magisk and manager and now cerberus not ask for root continuously

maybe is a bug of the last version with this app?

anybody use cerberus?

so.. i will reflash the backup of the system that i have..

I have not been able to uninstall the manager (when rebooting I was back in the application drawer) and if I installed the previous version with the last magisk it failed all the time, how should I have done it? flash the unistaller and then uninstall the manager ?, was going to uninstall it from the manager but showed a message that could be encrypted?"Root will be removed, and potentially encrypt your data if your data is not currently encrypted."
[Magisk] Aid777:
I installed the update on LG G6 stock already rooted ROM. Not noticed what version of Magisk it was , guess it was from 19.0 to 19.1. The update caused a boot loop though and using the latest uninstaller did not do anything to fix it.

I then decided to flash the latest stock ROM as the backup I had was old and only had a slightly newer Titanium backup. I flashed the BETA Magisk and all is fine. The update for v19.1 has popped up now and I am definitely not going to install within the app again.

Do you think it's safe to DL the latest ZIP and install in TWRP?
[Magisk] Ferr1s:
I was forced to Update magisk Manager to 7.1.2 and magisk to 19.1 and now Payback Pay Works! Thanks to the magisk Team.

I m using Mi8 with lineage 16

Gesendet von meinem Mi 8 mit Tapatalk
[Magisk] jcmm11:
Take a backup and try it. As usual it's working fine for most people but some people have issues and there's no way to know for sure which group you fall in unless you try it.

Save a copy of the TWRP install log after installing it and, if after booting you have a problem, post the log.
[Magisk] Pandemic:
On xz2 with pie magisk v19.1 give bootloop but v18.1 works fine so dunno why it happen :(
[Magisk] smart123123:
Hey... Are you using stock manufacturer android... Or have you done something else bcz your cts:profile is true...!???
[Magisk] Pandemic:
Did you enabled magisk hide in the settings of magisk and try to pass safetynet ? Should be true because i had the same on v18.1 and did that and works but v19.1 give me bootloop.
[Magisk] drezz2:
finally the problem of cerberus must be with magisk, not with the manager, I have reinstalled the last manager and there is no problem .. any idea ?
[Magisk] GlucoseFR:
Hello,

The Magisk 19.1 don't work on my Galaxy S7.

Magisk 18.1 is working and installed via a patched boot file from vanilla boot.img

Update to 19.1 from Magisk Manager 7.1.2 -> KO Stuck at Galaxy S7 splash screen

Update to 19.1 via patched boot.img -> KO Same as previous

Rollback via flash of v18.1 patched_boot.img -> OK

Detailled Setup Information :

Samsung Galaxy S7 - G930F

Oreo 8.0.0 Stock (Build R16NW.G930FXXS4ESC5)

Magisk 18.1 (18100)

Manager 7.1.2 (208)

With :

- Preserve force encryption

- Preserve AVB 2.0/dm-verity

No Xposed

No TWRP

Regards
[Magisk] pkn267:
Yes I have enabled magisk hide. But it didn't gave me bootloop.

---------- Post added at 07:15 PM ---------- Previous post was at 07:12 PM ----------

No bro IAM on custom Rom , and I didn't do anything special, just uninstall the previous magisk files you flashed properly and try to flash the v 19.1 zip that compiles the latest magisk manager with that as well. And do ensure magiak hide is enabled in the settings before safetyNet.

---------- Post added at 07:18 PM ---------- Previous post was at 07:15 PM ----------

IAM on custom Rom . Just do the following things .

1. Uninstall all the previous magisk files that u flashed using the magisk uninstaller zip.

2. Try flashing the latest magisk v 19.1 that compiles the latest magisk manager with it .

3. Try SafetyNet after ensuring magiak hide is enabled in the settings.

And I think this should solve your problem .
[Magisk] Ryder.:
With latest update the modules have been removed and i can no longer install them
[Magisk] Einheit-101:
V19 bootloops ASUS ROG Phone, reverting Magisk to v18 doesnt work, it says "magisk is not installed", a bug report has been submitted and deleted. What is going on here?
[Magisk] m i n a r:
For what it matters, same here. Oneplus One, ArrowOS, android 9. I was on 18.1, installed 19.1 when prompted aaaand bootloop. Downgraded to 18.1, still bootloop, uninstalled using the uninstaller and installed 18.1, bootloop, reinstalled the entire rom + gapps (with and without magisk!), bootloop.

No way to solve this at the moment, except wiping data, i guess. [MENTION=4470081]topjohnwu[/MENTION] , save us :D
[Magisk] JairPaalman:
Magisk is not installed (v19.1)

I've tried to install Magisk v19.1 on my S8 (SM-G950F running Android 7, stock firmware), but everytime I do so, when I open Magisk, I get a message saying Magisk is not installed.

Magisk 18 worked fine.

I've tried to do a clean install of Magisk in the following way:

* remove all modules and root applications and reboot

* remove the Magisk app and reboot to recovery (TWRP)

* flash the remove magisk zip and clear cache

* reboot and flash Magisk v19.1

* reboot to system and install the Magisk app

Still, the problem persist. Does anyone know what's wrong and how I could solve it?

Thanks in advance.
[Magisk] @kitokit:
Ive flashed magisk 19.1 in twrp, booted into system, does not pass safetynet check, i cant also enter recovery,...sony z2 rr pie. Any ideas?
[Magisk] Pandemic:
V19.1 have issues, better stay in v18.1 because that version rocks !! \m/
[Magisk] casouzaj:
I rum CarbonROM 7.0 (Pie, as well) in my Sony Z3C, with Magisk's latest Canary build, along with the modules which are shown in one of the attached screenshots, and I can pass both Safetynet tests. It's not exactly your case, but such data could mean something to you.
[Magisk] threeFatCat:
Magisk Hide is not working properly I think in the new version v19.1. I just noticed my bank app can now detect root and there are no recent updates that I received from bank app. Any suggestion? Is it possible to rollback to v18? Sadly I dont have Custom Recovery. :(
[Magisk] martyfender:
If you had any modules that were not updated to the new template, they were removed from the magisk repo on May 1, as [MENTION=4470081]topjohnwu[/MENTION] warned would happen. These removed modules will not show up in the MM downloads section. You may be able to download them from the modules thread though and install it through the add module option in mm. I have one such module and its zip file is still in my Android download folder.
[Magisk] guest4711:
Try hiding MagiskManager by repackaging it into random named app (Magisk Manager - Settings - Repack...)
[Magisk] kotuamoalt:
Maybe try 19.2? (Canary)
[Magisk] sco00262:
Samsung N960f with custum kernel can't flash 19.1 but 18.1 and 19.0 are fine.
[Magisk] levone1:
Questions for everybody, (trying to see what I can figure out...):

- Has anyone who has had update failed tried to flash v19 zip without updating Manager app, (seems like new Manager is possibly causing some issues)?

- Has anyone noticed if the results are the same whether you have screen lock set or not, or encrypted/not encrypted, etc.?

- Anyone who has update failed on Pie, do you have EdXposed installed?
[Magisk] wilsonhlacerda:
Working perfectly on LOS 14.1, Android N

On Play Store, download app "Rootbeer Fresh" and do some tests.

Try turning off / on Magisk Hide on settings.

Try hiding Magisk Manager itself on settings.

Try reboot.
[Magisk] martyfender:
Also, hide Rootbeer Fresh.
[Magisk] smart123123:
No bro... My magisk hide is on... But not able to pass safety net... Maybe there is problem with build.prop and should i replace the desired lines with stock manufacturer rom's build.prop??
[Magisk] jcmm11:
At this moment Canary 19.2 is the same as 19.1. Release notes for 19.2 state "Upstream release v19.1” and that's it.
[Magisk] threeFatCat:
Thanks for suggestion, it finally worked though. What I did is like this:

Toggle Magisk Hide under Settings if it's on already so: ON > OFF > ON - (Not the App with checkbox under Magisk Hide which I did a while ago)

After that, it will display Magisk v19.1 is not installed

Ignore it, then reboot

After that everything went back to normal. :good:
[Magisk] smart123123:
Can someone help me out with this!!!
[Magisk] jcmm11:
Uninstall then reinstall Magisk. Keep a copy of the install log. If you still have a problem post the install log, logcat (not a screenshot of a snippet), phone and ROM info.
[Magisk] smart123123:
Actually bro... I got this logcat of my settings app... There is root manager present in setting that when tapped opens the magisk manager and the magisk that was included in the rom zip was v13 and even opens successfully but after updating it to v18 or v19(latest) the settings app crash when we try to open it up from there...???

Although opening magisk from launcher works fine but not from settings app
[Magisk] Didgeridoohan:
In that case you're asking for support in the wrong place. That's something you need to ask the ROM developer about.
[Magisk] kosiak07:
Guys, after install Magisk 19.1v after install I have to enter password to decrypt devuce storage. In 18.1v everything is ok. Need help

Wysłane z mojego HUAWEI VNS-L21 przy użyciu Tapatalka
[Magisk] nullstuff:
android q beta 2 on google pixel (sailfish), here: following "successful" magisk 19.1 installation, system reboots to recovery (same behaviour as 19.0)
[Magisk] amk316:
Magisk v19.1 on galaxy s8

all banking apps don't detect the root except "STC Pay"!!! any help please....
[Magisk] guest4711:
Try MagiskHide Props Config Module (Magisk Manager -- Downloads). Probably you should finetune it.
[Magisk] shyvanna:
Magisk manager v7.1.2 crash after unlocking with fingerprint. This would result to the app not opening when you try to access it.

Device: Huawei P9

Android 8.1 RROS

Magisk v19.1
[Magisk] Ingan121:
Follow the 'Promon' section in https://github.com/Ingan121/UDSBypass. This guide works well for STC Pay.

The required string([package name]/[activity name]) is 'sa.com.stcpay/cpmcywcn.Ey4U4fTT'.