yashsingh1/xdaforums huggingface dataset:
[Magisk] jonners59:
The latest:

Manager = v7.0.0 (185)

Magisk = 18.1 (18100)
[Magisk] kotuamoalt:
That version is not stable. I recommend you either go back to version 17.3, which is the last known stable version if I am not mistaken. That is what I am using. Otherwise try one of the Canary builds until a new stable version is released through the manager. Hope this is helpful.
[Magisk] ahac85:
did you manage to install magisk?? im experiencing the same with P20 latest pie update .203
[Magisk] jonners59:
OK, just downgraded via Recovery. BUT now my Magiisk Manager does not work. So running blind unless I downgrade that too or leave as is to test and if works wait until the fix to upgrade.
[Magisk] kotuamoalt:
Ok. Version 7.0 manager is not compatible with any magisk version below 18.0, so you will have to also downgrade the manager to version 6.1 If memory serves me correctly, you uninstall the manager using the uninstall button when you open the manager. Then run the magisk uninstall zip in TWRP. Install magisk 17.3 via TWRP, then install the manager (6.1), and you should be good to go. Ignore the upgrade prompts that you will get when you open the manager until you see the new version has been released. (18.2). CREATE A BACKUP FIRST!

Good luck!
[Magisk] demonoidmaster:
>Not stable

Yet I've never had any issues, everything works

I don't get how do many people get so many problems with their devices and magisk, be it with modules, magisk hide, magisk losing root, etc
[Magisk] kotuamoalt:
As I stated previously, magisk manager 7.0 is incompatible with any version of magisk below 18.0
[Magisk] jonners59:
I did. Magisk Manager 6. whatever does not install, hence my meaning of running blind. I have no Magisk controls. I'm going to see how it runs, if the Google Pay starts again, and if anything else is affected. If pay works and nothing else seems to be upset I'll keep as is and just have to watch out for the fix before re-upgrading.
[Magisk] ag008:
Magisk hide doesn't work anymore? Latest 18.1. and maxtv to go says "System rooted can't play video"
[Magisk] kotuamoalt:
Does not instsll? What kind of error message are you getting?
[Magisk] jonners59:
It just says not installed... No reason.
[Magisk] kotuamoalt:
Did you run the magisk uninstall zip?
[Magisk] jonners59:
The first time, no, but the second time, yes, and then installed Magisk (though it installed first time I redid it to make sure, and then I rebooted and installed the manager apk....
[Magisk] kotuamoalt:
Then you should be good.

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

Try toggling magisk hide off/on.
[Magisk] Didgeridoohan:
Maybe:

https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_install_the_Magisk_Manager
[Magisk] jonners59:
SORTED, thank you.....

I am now back in time. :)

PS; whilst on this thread and your undivided attention. I noticed that after I installed my Superman rom and started to set it up and install the apps, the phone encrypted the /data directory. I do not think it was the Superman ROM as that would have been done during the build or as soon as I opened it up, so I SUSPECT it was Mugisk, but I don't know. So my question is, would, does Mugisk encrypt the phone or do I need to look elsewhere for the culprit? The problem is that now TWRP can not back up the /data directory and every time I open it, I have lost all my settings.
[Magisk] Didgeridoohan:
[MENTION=3020660]jonners59[/MENTION] It's perfectly possible for Magisk to keep the forced encryption enabled. Either if you enable it when installing, or if the installer detects that you have an encrypted device already. Hard to know if it's actually Magisk without seeing the installation log...
[Magisk] jonners59:
I am thinking that the Magisk, that comes with the superman rom has the encrypt ticked by default in the image so once the rom has had a chance to settle down the Magisk encrypts /data. I suspect as after first install, i tried again after deleting data and managed to save the /data directory after the first boot, but once it started all the setup when i tried to re do the updates /data twrp couldn't find it as it was now encrypted.... hope that makes sense.
[Magisk] martyfender:
As many have said, it is a bad idea to include Magisk in a ROM, for many reasons. Are you aware that there are twrp terminal options to disable forced encryption and dm_verity when you flash Magisk.

? You should be able to find documentation for it.
[Magisk] jonners59:
I didn't make the rom, though bar this it is a good one.

So you are saying both dm_verity and forced encryption should be disabled to get waht I want. But once done it can not be reversed unless i clear data again and start over, yes?
[Magisk] martyfender:
Yes when you disable it you must delete data or factory reset so a new, unencrypted partition is created. The same is true if you want to re-encrypt.

Here is a link where the terminal options are listed:

https://www.didgeridoohan.com/magisk/MagiskInstallationIssues
[Magisk] jcmm11:
I believe that when you encrypt it encrypts the existing data (which is why it takes so long) and you only have to delete when decrypting.
[Magisk] martyfender:
Yes, you are correct and I wasn't thinking about it, since my devices were only encrypted when they were new and several of the newer ones I rooted with magisk during the first or second boot, so I am not used to an encrypted device.

Thanks for clarifying that mistake I made.
[Magisk] Windowlicker001:
From good start to bricked! Please help!

Hi Community,

I am somewhat embarrassed to have taken good advice from a community member, achieved root of my tablet through Magisk Manager, only then to have done something that led to apps crashing before they fully opened. My rash decision was to then go through the process I had previously done to get to a stable place again - I flashed the stock rom through ADB shell command with a view to reinstalling Magisk and patching the rom again, but now it would not boot up beyond the boot up screen. I put it back into recovery and wiped cache and user data for factory reset and flashed the stock rom again. Now I am in an eternal mess where I cannot switch off the tablet - literally! No amount of hard key pressing will now give me the recovery screen and all I have is the fallen Android man with red triangle flashing onto a black screen every other second. At the bottom it says "supported API: 3'. I cannot switch off, reboot, communicate with shell commands, or get to the recovery screen! Is this something to do with the Dalvik cache, or did I manage to clear that when I wiped cache from recovery screen prior to flashing?

I really hope I am not someone who has literally ruined my device and no one can help.....I would be eternally grateful for any assistance anyone can give!

Specs:

Screen - 10.1" HD 1280x800 IPS Capacitive Glass screen Touch Screen (10 point)

CPU- Quad Core 4x1.5GHz (4x Cortex A53)

GPU-Mali-T720 MP2@600MHz2

Memory (RAM)- 2GB DDR3L E1R16 (2017)

OS - Android 7 / 6

Bluetooth - Yes

Built in memory - 16GB( around 11GB is free, rest is used by android system)

Memory Card Slot micro SD up to 256GB

WiFi - 802.11b/g/n 5&2.4 GHz

Camera -2MP/2MP (HD recording)

Sensors:G-Sensor

HDMI: Yes (mini)

Battery 7000 mAh up to 13h

Ports - Micro USB (OTG)

---------- Post added at 04:12 AM ---------- Previous post was at 03:51 AM ----------

Just to inform you further, bootloader is unlocked (verified on boot up screen)
[Magisk] KaMyKaSii:
From what I know it is not possible to install a rom through adb shell, did you mean fastboot? Could you describe exactly how you installed the stock rom?
[Magisk] martyfender:
I believe that is why you can't boot up with the stock rom, your bootloader is unlocked, so it does not pass verification? I'm not sure though, why it is locked up.

You posted all of the device specs, but not the device name. And what do you mean: OS - Android 7 / 6? You don't remember if it is Android 6 0r 7?

It sounds like you are stuck in fastboot/bootloader mode, though. Usually one can do a hard shutdown by holding the power button for about 10-15 seconds. However, it appears you have tried that already.

Hopefully someone else has some better idea. Was your recovery a stock one or is it a custom one such as TWRP?

One time, on my older, now dead Nextbook Ares 8, Android 5.1 tablet, it was stuck similar to that and I had to carefully remove the back and unplug the battery to be able to boot it up again.

I would advise only attempting that as a last resort, because it is easy to damage or a static discharge could break the tablet also.

Do you have fastboot installed to your computer in addition to adb. You mention shell commands and those are used when the tablet is booted normally. you would use fastboot commands in bootloader mode you appear to be in.

For example: fastboot flash boot boot.img

fastboot boot twrp.img or what ever it is named, to temp boot twrp recovery you have on the computer, usually in the adb/fastboot folder to make it easier. That is assuming you are on Windows. I use Linux so it is a little different, but basically the same, with the addition of sudo before the fastboot commands.

fastboot devices

will tell you if your device is connected to the computer. You should see the fastboot serial number which will be different than when the tablet is booted normally and you type: adb devices.

---------- Post added at 01:52 AM ---------- Previous post was at 01:27 AM ----------

Yes, I wondered about that myself. normally it would be installed through fastboot in bootloader mode, or on some devices it is called download mode. For example, Samsung devices have to be flashed in downloader mode with Odin, not fastboot. I also wonder if it is an a/b device, which would mean the recovery is in the ramdisk of the boot.img. Flashing the stock boot.img might have been enough.
[Magisk] jonners59:
Thank you. I do not know if this was the case, I can only assume as I did not ask Spiderman to encrypt. When feeling brave I'll give it a go. It takes so long to get everything back, even when Titanium is working.
[Magisk] warrencoakley:
Since the last Google Pay update I'm getting that my cards within Google Pay cannot be used for shopping it states. Is this something they have one in the recent update with Google Pay that causing this issue with Magisk? It was all working smoothly until the latest update.
[Magisk] warrencoakley:
This is what I'm getting. It was working fine. Last transaction was last Wednesday.
[Magisk] Stan464:
Yeah, same Magisk version as mine. i actually Disabled Contact less and tried to Re-Setup. it wouldn't even let me set it back up. So if i was you. dont Disable / Configure your Google Pay again.

Phone: Huawei P20 Pro

Magisk: 18.1 Stable (was on 16.1)

Magisk Manager: Latest Stable
[Magisk] Mixedability:
Apologies, for clarification:

Tablet is a Neocore E1 (Android 7)

I installed the stock ROM via fastboot (apologies, didn't mean ADB...I use that to reboot to recovery when attached to my Mac), using 'fastboot flash boot /stockrom ..'.

When everything was good it was because I had patched the stock ROM through Magisk v18.1 as per instructions. It was this process that I was trying to repeat when I got into a mess.

Just to clarify:

Neocore E1 tablet running Android v7.0. Unlocked bootloader.

Stuck with red triangle dead Android man flashing and no way to shut off (simply reawakens), hard pressing keys into stock recovery screen doesn't work anymore.

Currently awaiting battery to die as I don't know what else to do...
[Magisk] chooks06:
Long press on power and volume DOWN combination seems to work for some devices. Longest I ever held down on my Ulefone Armor X was about a minute.. Not sure about other devices.

However, in some cases, it could go back into reboot. Got to release the buttons at the right time.
[Magisk] jsgraphicart:
Ok, it's not just me then. The weird thing is, it works at some places and not others. It hasn't been working for me at gas pumps or restaurants but I was able to get a soda out of a Coke machine using it. I guess Google is at it again with Google Pay.
[Magisk] razorsbk:
Pixel 2 owner here:

Hi guys. After the latest march update I can no longer use android pay for nfc payments. I'm rooted with magisk 18.1 and every checkmark is green.

I've hidden the root from all play apps, but somehow Google still detects my phone is rooted and I can't pay with nfc.

Anyone here with the same problem?
[Magisk] jackyip:
My phone is Xiaomi MIX 2. I have the same problem even the SafetyNet check is successfully passed and the device is certified by Google Play.
[Magisk] KaMyKaSii:
Just to make it clear, did you install the stock ROM only with this command? Because from what I know it is only possible to install the stock rom through fastboot with just one click through the command "fastboot flashall" or some sh/bat script. If you used only the "fastboot flash boot [...]" command, it means that the only partition you wrote is boot partition, it was not a full stock ROM installation. And when you said you did this for the first time and got stuck on the boot screen, you were talking about boot logo (a static image of your OEM) or bootanimation (the cool animation)?

So is it possible to turn off but turn on again soon after? I've been through this before, are you sure you're hitting the timing? If you hold down the power button for half a second or more after turning it off, it will probably turn on again. And have you tried instead of keeping just the power button pressed, hold down all the buttons needed to get into the fastboot until the device turns off and on again?
[Magisk] Itachisasuke:
Known issue with newer versions of Google Services Framework. Another thread is going on as well. Bottom line is that it's temporal in nature when root is detected and we'll have to do some more investigation and digging to see how exactly it is being detected and if it is preventable, and/or actionable. It seems that people are mostly having the same results with the temporal detection regardless of the versions of Magisk and Magisk Manager Installed. Some people have reported that running in Magisk Core Mode is slightly more stable but I haven't seen any testing evidence to support that in any of the threads.

Even after resetting all of the Google Pay and Google Services Framework and Data with a fresh install of Magisk, it is only buying you 4 days of use before its detected again. That data wipe that's required also takes a bunch of other data with it, unrelated to Google Pay.
[Magisk] Rushmed:
Hello,

I am on Soldiers s9 rom and magisk was always working.

Last week I hit accidentially uninstall in magisk manager and after that the only way to bring th phone to life again was to flash a stock samsung rom via odin. Than I restored a TWRP backup an everything seems to be ok so far.

But everytime I flash a new rom with magisk or even a single magisk zip the manager tells me magisk is not installed and root is not present. Its possible to restore boot backup with TWRP but since latest rom version needs firmware update i get stuck. Phone always locks itself without letting me do anything.

Can somebody help?
[Magisk] warrencoakley:
Tried rolling back to a previous version of Google Pay thinking this might resolve the issue as the latest update was March 14th and no dice. Tried getting a soda from a machine in work and still getting the attached error. As I said it seems to have only happened since last Wednesday. I hope there will be a work around soon. If you do find one let me know.
[Magisk] juergenh99:
18.2 (18118) works pretty fine for me, since several days without issues.

Root still hidden for Ms intune and banking apps for example.
[Magisk] warrencoakley:
My banking app works fine. The break was the update in Google Services and Google Pay will not work
[Magisk] Alan-B:
Hello,

Small problem with the version 18.1 in .zip in a custom rom, magisk seems to be installed but is not!

Works only with version v18.0 and then update.

PS: Rom HTC U12 +

An idea of the problem ?

(Thank you for the work)

---------- Post added at 10:54 PM ---------- Previous post was at 10:54 PM ----------

Hello,

Small problem with the version 18.1 in .zip in a custom rom, magisk seems to be installed but is not!

Works only with version v18.0 and then update.

PS: Rom HTC U12 +

An idea of the problem ?

(Thank you for the work)
[Magisk] TomeG2kc:
WHY (look screenshots)?

I'm not sure when it's happens but it works few days or weeks ago. Of course I've Magisk Hide and Magisk Hide Manager on.

I've tried Magisk Core Only Mode - AND IT'S WORKING!

But I need some modules to work...

I've tried MagiskHide Props Config too but isn't help.

Any suggestions?

Link to log:

<iframe src="https://onedrive.live.com/embed?cid=00653FD16A6F9ACA&resid=653FD16A6F9ACA%21927&authkey=AM-nuBl8-p3lnrQ" width="98" height="120" frameborder="0" scrolling="no"></iframe>
[Magisk] yung40oz84:
Go to the Google pay thread. There are solutions there, but everything is short term and it's going to keep doing it.Trust me when I say I've been through it for wks and tried every solution/scenario posted and my own. Sometimes works for 3-5 days, sometimes 1 payment, sometimes immediately reverts. It's obviously something Google changed in March update so just have to wait till Magisk finds the fix or solution. For now accept reality, either run core only, lock ur bootloader, or don't use pay, lol.

---------- Post added at 12:41 AM ---------- Previous post was at 12:40 AM ----------

U need to go to the Google pay discussion thread
[Magisk] wrecklesswun:
I think the issue with google pay is more wide spread. I am having the same issues, non rooted completely stock on my galaxy note 9 and essential ph-1....
[Magisk] Faithful4real:
I have tried uninstalling magisk root and install it again but still no root access
[Magisk] zputnyq:
It happens to my device as well.

As the solution u have to check whether it's installed on external or not first but if it is non exist then u can uninstall magisk then install the latest zip. After it, install its manager (magisk manager)
[Magisk] Mixedability:
Apologies...work/sleep and I'm back worrying about my issue.

Fastboot and ADB installed my Mac and prior to the issue capable of full communication with the tablet.

Thank you so far for your collective input.

On reflection, should I have dragged the entire stock rom folder into Mac OS X terminal to write 'fastboot flash boot /(stockromfile) flashall'? I wrote 'fastboot flash boot /(stockrom.img). If this is the case then is the problem of not being able to get to recovery beyond the flashing red triangle screen based on a newly flashed stock recovery (in the stock ROM folder) not being present at the same time the verified-boot.img is flashed?

If this is the case then I have pulled apart the compiled install components in the stock ROM folder provided to me by Neocore and focused only on the rom image file and discarded other components necessary for successful install.

I would be grateful for clarification process for successful flashing of both stock recovery and rom through shell command using fastboot.

None of this resolves my current issue however. To clarify, the tablet is constantly flashing red triangle and I cannot successfully press the button sequence to get to recovery screen...it simply ignores and begins with the Neocore boot screen before flashing red triangle again

The only respite I get is to poke the reset hole and it stops. Touching any hard key though and it's back to red triangle screen!

I am eternally grateful for any advice...
[Magisk] jonners59:
As pervious posts......

---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------

Actually, downgrade Magisk and Magisk Manager after uninstalling... See previous threads.

---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------

I have unticked the encrypt option in Magisk, but it keeps coming back, is that because it has now encrypted the /data partition?

I am going to struggle to create an unencrypted directory if this is the case, as it will always default to encrypt and so encrypt my phone even if I start over, no?

It's a shame it doesn't have an unencrypt option... That would be nice. :D Sweet dreams.
[Magisk] vetSamet:
hi everyone i have moto z running android 8 rooted with magisk on stock rom. i install the module pix3lfy a few days ago. and i want to uninstall the pix3lfy module today. it says pixelfy uninstall after reboot. and i reboot and BAM! its stuck on bootloop now.

how i can fix it. ?

is the only chance the wipe data ? thanks
[Magisk] Didgeridoohan:
The forced encryption option in the Manager only has any function when you actually install Magisk or patch a boot image. Since you're now encrypted you will have to either reinstall Magisk with that option unchecked, or disable the option prior to installing Magisk through recovery (details here). You're also going to the to format /data after you have disabled the encryption flag.
[Magisk] Swierk:
Do I really should trust you? Use core only?

Core only let me add a card successfully but fail in completing NFC payment at terminal.

Did you checked downgrade to 17.3 AND downgrading Google play services WITH properly forceing not to update itself ???

Sent from Xperia Z5, stock rom 7.1.1, 32.4.A.1.54, Magisk 18.1
[Magisk] Marcondes BR:
Root Moto G7 Play

Hello. I have a moto g7 play with android 9 and I can not get root with magisk. I followed the step by step of "Boot Image Patching".

My bootloader is unlocked.

The boot.img image is correct.

I do not get root and magisk says that it is not installed.

Can anyone help?

Magisk manager version is 7.0

Magisk version is 18.1
[Magisk] KaMyKaSii:
You'd better try with the latest Magisk Canary Debug build. If it still does not work, you should create an issue in Magisk github with the necessary logs and files

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337/post77549897
[Magisk] Didgeridoohan:
What's the point of this post, apart from advertising possibly scammy websites?
[Magisk] Nebrassy:
In my experience, that never worked for me, I formatted data and made sure to disable "preserve force encryption" option and that never worked, the only way to disable it is to flash http://zackptg5.com/android.php#disverfe first which will modify fstab in vendor, and then flash magisk
[Magisk] jonners59:
THANK YOU!!!!!!!!!!!!!!

That would explain a lot. I have downloaded and will add to my phone and give it a go.

Do I still need to delete /Data and start over?
[Magisk] Nebrassy:
If it's encrypted then yes you should format it with twrp or wipe it with fastboot, then flash that zip then flash magisk
[Magisk] watchman759:
I think I have 3 easy questions but cant find answers. 1- if I flash a boot .img it removes magisk correct? I am unsure of my boot image as I loose root some times. 2-Phone wants to install a security patch. Should I install that image of is there a way to "turn off" magisk, install and turn back on (I thought I saw a post about that but cant find now). 3- I am trying to install ikeymonitor to monitor my sons phone but just can't get it to work well with magisk. anyone else had this issue? Thank you so much.

sorry also forgot to ask, would changing boot .img erase any phone data?
[Magisk] Swierk:
Transactions in shops working flawlessly :)

Android 7.1.1

Magisk 18.1 in full mode

Menager version doesn't really matter but 7.0

Newest Google Pay 2.84.x

Moded Google play store 13.1.32

What I did:

1.Download Google play services 14.7.99 (last working)

2.Removed all administrator apps from settings (apps that can change android settings)

3.Airplane mode

4.Uninstall Google play services update

5.Clear it's data

6.Install 14.7.99

7.Disable mobile background data for Google play services and Google play store

(I do not prefer auto apps update)

8.Using Disable Service apk disabled service of Google play store named: GmsCoreUpdateService

9.Reboot

10.Get back settings for administrator apps

Sent from Xperia Z5, stock rom 7.1.1, 32.4.A.1.54, Magisk 18.1