yashsingh1/xdaforums huggingface dataset:
[Magisk] vukis:
I shared apk extracted from titanium backup apk.gz (lt.swedbank.mobile.v2-ab6311c130223bef1c87a3f1e1c2a264.apk): https://saugykla.telia.lt/Shares/Home.aspx?ShareID=f45b1c1a-6538-4744-a881-e0c4021f5a6b

It's mindblowing, that it is working for you even without hiding magisk, and it was not working for me without being rooted (but unlocked bootloader).

Anyway I downloaded magisk-release.zip and magisk-uninstaller.zip canary from https://github.com/topjohnwu/magisk_files/tree/master/canary_builds.

1st atempt

Ran magisk-uninstaller.zip from TWRP install cleared cache and restarted recovery. Got into problem that it did few restarts and booted into recovery which didn't ask for patern lock.

Sideloaded magisk-release.zip. And tried restarting. Got into bootloop.

Recovery still accesible, but sdcard was shown as encrypted so my fresh nandroid backup was inacesible. Sdcard was mounted on PC, but folders and files was encrypted and was not posible to create any files or folders

So I did flash all via fast boot restarted went through all fresh start wizards and coppied a bit older nandroid backup. Then boot / sideloaded twrp-3.2.3-37-fajita and restored older nandroid backup (boot+data).

Any easier way resolving this when recovery does not offer patern lock for decrypting sdcard? And why did it happen only after magisk uninstaler, what I am doing wrong?

2nd atempt I played safer:

Tried magisk-uninstaller.zip from canary build github (install via twrp install). Then tried installing same magisk-release.zip without recovery restart. It ended in errror:

Invalid image: not signed
- Unpacking boot image
Parsing boot image: [/dev/block/sde11]
! Unsupported/Unknown image format
- Unmounting partitions
Updater process ended with ERROR: 1
I:Install took 5 second(s).
Error installing zip file '/sdcard/magiskcanary_20190313-release.zip'

Similar error when trying to install Magisk-v18.1.zip

So I restored boot partition from fresh nandroid backup and restarted recovery. Then tried uninstaler from this post of this thread: https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337

but it ended on similar error upon installing. Restored boot partition again. And resized that I am doing something wrong on uninstalling via twrp...
[Magisk] Chamelleon:
I don't know exactly when it happened but Google Pay is not working anymore on my phone. I can't add a card to pay contactless. Magisk Hide on and GPay on list. SafetyNet pass and both options on green.

Log in attachment.
[Magisk] tyler19820201:
I have got the same issue around two weeks ago. I was trying to update from los 15.1 to 16.0 via dirty flash but did not help. Then i did clean install and now works perfectly. I am using OP3T.

The problem was for me is just the google play services was disabled all the time and could not turn on enabled.

Did you check google play services are enabled??
[Magisk] Solid_Eye:
I hope you're right, what was broken were banks apps, banks form different countries (4 banks in total)! and also google pay! I'll try to install it since I just reverted back form Android Q. thank you guys no matter the results :p :laugh: :crying:
[Magisk] iMystic:
I k

Nu lkl to am k
[Magisk] Chamelleon:
I just reinstalled Google Services to be sure but it didn't help. Google Services is working properly because I can use maps and I can open Google Pay but can't setup contactless payment.
[Magisk] tyler19820201:
Yes this is was my problem also. On magisk safetynet verification was ok. Also googleplaystore was workig well and googlemap also. Every google apps was working well. However the google play services module was just "frozen" on the app list. I mean the forced disable or enabled button was just not tapable!!! It is strange but this is what i was experiencing. Go to settings apps and search for google play services and make sure system apps are visible and search for any google related modules. Check them are enabled!! Google maps, playstore etc works for you this means nothing in this case
[Magisk] Chamelleon:
It's not frozen, already checked.
[Magisk] tyler19820201:
Well i would recommend a clean install then. I have no more idea:rolleyes:

Do you use Gapps?? If yes this might be a problem. Install a new gapps package could sort out this issue...
[Magisk] martyfender:
https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
[Magisk] Chamelleon:
It worked. I know that it's just temporary solution but thank you.
[Magisk] martyfender:
I recommend reading further in the thread for some more potenially longer term solutions, such as play services beta, etc. For some after doing their recommendation in post 5, it never fails again. So keep it the way you have it now until it fails again, if ever. Some of the successes may be also be due to fixes Google has done, also. I don't use gpay, but find the thread of interest to read, since questions are asked about it so often here.

Also see some have had success by leaving the play services beta program.
[Magisk] GovernorKeagan:
I've had a similar problem on my Huawei P Smart (2017 version). Difference is that if I install any module, it freezes on my boot logo sometimes. I then have to force a shutdown, and hope nothing gets "broken" in the process. I've had to do a factory reset twice already and I've been rooted for a week.
[Magisk] Stavrozo:
saftynet fails both ctsprofile and basicintegrity

Hi all

I have a rooted Huawei honor 6x (BLN-L21) with Magisk 18.1 and EMUI 5.0 android version 7.0 ....everything was working until I updated magisk to 18.1 it seems that magiskhide is working because my banking account is working fine but the safety net status check is always false in both the ctsoprofile and the basicintegrity.... i had tried everything core mode only , toggling the magisk hide in settings, uninstalling magisk and reinstalling it nothing works ? so is there anyway this can be fixed

Thank you

stavros
[Magisk] BrimoFan123:
I have latest Magisk 18.1 installed on LineageOS. It's running very well. ctsProfile and basicIntegrity are true. Magisk hide allow me to use google pay, outlook, bank application. The problem is that randomly II'm loosing SaftyNet checks. Both ctsProfile and basicIntegrity "switching" to false. I did not found in which scenarios it is going to false. Smartphone reboot is the only way to get them again true. Is there a root cause why it is happening?
[Magisk] sdamark:
Known issue, toggle hide on and off should be all that's needed. No need to reboot. Should be fixed on next release.
[Magisk] ashyx:
Surely the sensible thing to do is simply spend 2 mins making a device backup with TWRP prior to modifying or installing anything rather than factory reset? :silly:

Shakes head...
[Magisk] GovernorKeagan:
Yeah... The first time TWRP didn't see the backup for some reason. Second time I just forgot to make the backup.

Just curious why it seems to do this?
[Magisk] Airtioteclint:
I'm on 17.2. How do i upgrade while preserving dm vetrify and forced encryption.

Update from magisk manager downloads 7.0 and doesn't support anything less than version 18.0 forcing uninstall.

Is there a way to flash updates in twrp while keeping dm vetrify and force encryption?
[Magisk] lchiu7:
Will 18.2 fix Gpay issue? Can I just flash the Canary build?

Like many in this forum Google play stopped working suddenly because I guess Google updated its Google play framework. I'm on my Magisk 18.1 and it seems that 18.2 canary build will fix the problem temporarily. Can I just go into TWRP recovery and flash the 18.2 zip on top of my current version? This is on a Moto Z2 force running a fairly stock ROM.
[Magisk] girkev:
Can't get setup Magisk in the latest 9er ROMs for Shani.

Concerns not the latest lineage is

Any help please

Cheers
[Magisk] H4X0R46:
Are Magisk modules persistent across rom flashes on an A/B device or are they wiped when a new rom boots? I guess my question is, are modules run from userdata?
[Magisk] jcmm11:
You should be able to do that and it should work just fine.

However, as always (and especially when using bleeding edge releases), you should be prepared to handle a situation when things break. (And if things do break grab logs and post bug reports in the proper channels)

But again - it should work just fine.

---------- Post added at 01:47 AM ---------- Previous post was at 01:44 AM ----------

Yes they're run from userdata. All the modules are run from /data/adb/ (beyond that general location specifics depend on the release your running)
[Magisk] Windowlicker001:
Stuck in eternal boot loop after Magisk patched recovery install

Hi,

I used Magisk Manager to download latest Magisk app to patch the stock recovery.img on to my unlocked/unrooted Neocore E1 tablet.

All seemed well; I copied the patched recovery image back to my Mac, opened terminal, used the fastboot flash command and the recovery seemed to install (a message on the tablet said 'transmission complete'). Unfortunately though, as there is no custom recovery on the tablet (hence patched recovery method), I cannot seem to do anything other than watch as the tablet boots, goes blank and then tries to reboot again.

ADB through terminal command cannot see the device when plugged into usb (obviously usb debugging was switched on when flashing the image). So I can't reboot from there and no amount of button pressing combinations on the tablet do anything. I finally found a small reset hole which I poked when also pressing power button. This has finally turned it off but the same boot loop again on restart.

I am new to rooting and was given hope when I managed to root my Redmi Note 4. Now however I am lost and really hoping some kind soul can help me stop this eternal boot-looping whenever there's power into this tablet!

Neocore E1 tablet (unlocked and unrooted) with boot patch attempt to install Magisk latest app version through Magisk Manager app. No TWRP

Mac desktop using ADB and fastboot terminal commands only recently learnt

I will be very grateful for any kind assistance.....S
[Magisk] ashyx:
I know nothing about this device, so I'm just intrigued and a little confused.

Your device uses the recovery partition to boot? :confused:

Is boot and recovery somehow combined?
[Magisk] H4X0R46:
So it's a good idea to delete the modules so they don't persist into the next rom flash then?
[Magisk] Allstar007:
Hello I try to install on my Samsung Tab S3 (T825) all the time. Everything is installed in TWRP, but I have the app and no root rights. Can someone help me how to get this to work?
[Magisk] lchiu7:
---------- Post added at 01:47 AM ---------- Previous post was at 01:44 AM ----------

I got stuck alas. I tried to boot into twrp (I had used twrp to flash a slightly customised version of the Sprint ROM to remove carrier lock as well as Magisk so I know it was installed) and it booted into stock recovery.

Since that time my PC had been rebuilt and I lost all the drivers etc. for the phone and so reloaded them all (it seem successfully).

Booting into fastboot works okay and I can type fastboot devices and see the Z2. But fastboot boot twrp.img to reflash twrp just hangs. Now sure this is relevant but in fastboot mode no adb commands work either.

Guess I will have to wait until Magisk 18.2 goes GA and until then just use my CC card :(
[Magisk] martyfender:
If it is an A/B device, the recovery is in the ramdisk of the boot.img if my memory serves me correctly. I thought that you are not supposed to use fastboot to flash recovery on such a device? On A/B devices there is not a separate recovery partition.

I have not re-read all of it, but here is a guide:

https://xdaforums.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123

The links in it are very informative, also. would like to thank the person who posted these links in one of my posts months ago, I just don't recall who to thank without extensive searching.

Someone please clarify, since I don't have any A/B devices.

Thanks

---------- Post added at 02:06 AM ---------- Previous post was at 01:57 AM ----------

Adb commands don't work in fastboot. Adb commands only work when the device is booted normally. If I am not mistaken, you can also adb sideload in TWRP.
[Magisk] moloko01:
No one else got this problem?
[Magisk] Windowlicker001:
I'm not sure if it's new but it's marketed as 'British'. Nice glass screen for less than £100 + 2 yr warranty. Specs are:

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

I wanted to route it and read about Magisk using the stock rom and patching it to make a custom rom. As I can't find a custom rom for this device I asked Neocore for the .img of the stock rom, which they happily supplied, because the Magisk patch seemed the only viable option. I downloaded the Magisk Manager app to the tablet and did what it said....I navigated to the stock rom file and clicked patch. It said it was successful, so I downloaded the patched file to my mac where I opened terminal, ran adb and found the tablet (usb). I typed 'fastboot reboot recovery' and the tablet rebooted and gave me the option to reboot to bootloader, which I did. Once in fastboot mode I ran terminal command fastboot and the typed 'fastboot flash boot /.....and the file location. I hot enter and the file installed. I shut the tablet down and then turned back on - that's where it is now...endlessly rebooting!

I hope that helps you understand where I am now......
[Magisk] ashyx:
But that's what confused me. He actually stated he'd patched the recovery.img?

I thought I'd maybe missed something somewhere in the development of Magisk as this thread moves so fast.

---------- Post added at 09:57 AM ---------- Previous post was at 09:51 AM ----------

Can you clarify what images you were supplied with in the stock firmware?

When you say recovery.img, do you actually mean the boot.img?

Also if its boot looping this is likely because of dm-verity. This should be patched by Magisk, but it wouldn't work if you have patched the wrong image.

Fastboot is a bootloader function so irrespective of whether it's boot looping, you should still be able to enter fast boot mode using the right combination and timing of the hard keys.

Maybe you're just not holding for long enough or at the right time.
[Magisk] vukis:
Anyone have a clue why uninstall zip locks recovery and other issues?
[Magisk] jonners59:
Google Pay stopped working Magisk v18.1

Samsung S7 SM-G930F running Superman ROM v3.0.18, Android version 8.0.0 and Kernel 3.18.120- SuperManStock_SM-G930F_V3.1.0

Magisk Manager v7.0.0(185) and Magisk v18.1(18100)

In the last two days I have NOT been able to use GooglePay. I have heard it is since Magisk upgraded to 18.1, but I am not certain.

Can I please confirm that this is a known problem and if it is being resolved, please?

I would also like to know if there is any immediate solution to this problem?

Thank you.
[Magisk] teddy0209:
Canary... It's the latest, you should try it as most issues from the stable build has been resolved there... It's a requirement by the way before reporting an issue.
[Magisk] martyfender:
https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703

See post 5 but I would suggest further reading in that thread.
[Magisk] Rhino42:
Hello Community,

I have a problem I haven't been able to solve so far. Straight to the point: I can't load any modules manually in magisk. When I tap on the "+"-Button in the modules-Section, my default File Manager will pop up and show directly all the modules I loaded so far from the Magisk native repos as well as the ones I downloaded manually, as it should be. However the modules (zip-files) I downloaded manually, the ones I want to use, are greyed/unusable. The other modules which come from the native repo of Magisk are perfectly usable. All permissions for Magisk set.

Everything else on my phone works like a charm. I did research this issue and found nothing useful. I have no clue why this would happen, since the flashing/rooting processes also worked flawless. Am I just overseeing something or is anyone else having this issue? Please help me out:confused:

I have a Galaxy S8 Exynos, custom flashed with TWRP/AlexisRom/android 9 Pie; Magisk 18.1(18100)/Magisk Manager 7.0.0(185) was included in the Rom . I also uninstalled/reinstalled Magisk as described in the Wiki, what also worked perfectly. But again exactly the same issue, nothing changed

Any answer/help is so much appreciated in advance!

Since this is my first post on xda, I feel I also have to say deeply Thanks to everyone who is making ROMs/CustomModding/Rooting possible and especially Thanks to Magisk-Team since I'm here and asking.

Rhino
[Magisk] Allstar007:
Hello I have finally rooted with magisk this Rom,

-> https://xdaforums.com/galaxy-tab-s3/development/rom-crdroid-5-1-android-9-0-20190211-t3899276

but Magisk shows me at SaftyNet the: ctsProfile: False.

I have already hidden all apps with the hiding function but it still does not help. What can I do?
[Magisk] jcmm11:
First of all do NOT "hide all apps". You should only hide things that are explicitly problematic because they detect root. Hiding everything is likely to lead to problems because of the way that Magisk works.

Next, for the CTS profile problem see https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228
[Magisk] Windowlicker001:
Apologies for the delay.....I finally pressed the right button for long enough and now its in the stock recovery screen.

The stock images in the file are plenty, but I think the relevant ones are 'recovery-verified.img' and 'boot-verified.img'. It's not beyond possibility that I dragged the recovery image into terminal. As I'm now out the loop can you kindly advise on what you would do now? I just want it rooted and for a custom recovery installed to try new roms. I keep reading that this latest version of Magisk has caused other boot loops with people and advise is to find an older version.

I do have a custom recovery and boot file for this tablet which I found on needrom. However, I'm not savvy enough to understand the install instructions.

I apologise for my general ignorance but very grateful for any advice I can reasonably follow...

S
[Magisk] AndrzejDwo:
When you tap + in modules and default manager pop-up you have to tap 3dot menu on the upper right side and then tap "show internal storage" and then on the left side choose your internal storage/download and all the zips will be available.
[Magisk] guest4711:
MagiskModules are normal archives having a 'zip' extension. Are the files you downloaded still zip-archives?
[Magisk] ashyx:
Well in reality you need to put it back to stock to get it booting again whether that means the whole stock firmware or just the recovery image.

Then you need the boot image to patch with magisk.

However, you have stated that you have a custom recovery available. If that is indeed the case then I suggest to use it to first backup your stock boot image then install Magisk.

If it doesn't boot restore the boot image and try another version.
[Magisk] Rhino42:
Aha. That did the trick. I'm so eternally grateful. Thank you!:good::good::victory:
[Magisk] Windowlicker001:
Thank you - I'll do just that.

Thanks for helping me asphyx....I'm very grateful.:good::)
[Magisk] HaloTechnology:
MAgisk seems no longer allow us to use Google pay even though I am passing safteynet google pay now says "you are no longer able to use google pay in store ".

I checked all my modules its not them .

---------- Post added at 04:31 PM ---------- Previous post was at 04:31 PM ----------

MAgisk seems no longer allow us to use Google pay even though I am passing safteynet google pay now says "you are no longer able to use google pay in store ".

I checked all my modules its not them .
[Magisk] lchiu7:
Thanks. I'm also wondering if the flash of TWRP is failing because the phone has a fingerprint lock because all the documentation I've seen says to unlock the phone completely before flashing.
[Magisk] HaloTechnology:
after some testing google pay only works now in core mode only :(
[Magisk] Hydro8:
Hi

I try to use magisk with lineage os 16 on my oneplus3 but I can't install.

I attach the error I've got when trying to wipe.

Thank for the help !
[Magisk] Swierk:
Have you tried older versions of Google Pay?

Sent from Xperia Z5, stock rom 7.1.1, 32.4.A.1.54, Magisk 17.1
[Magisk] Itachisasuke:
Same here. Another Thread on this is going here as well.

It seems to work in Magisk Core mode only right now. I just used Google Pay Tuesday at the gas station, I tried today at the same gas station and no dice.

"You can no longer pay in stores with Google Pay"

Pixel 2 XL

March 2019 Security Update

Magisk 18.1

Magisk Manager 7.0

Google Play Services 15.0.90

Going to attempt the Magisk Canary Build and try the vending machine at work Monday

Edit: I should note that SafetyNet and CTS Checks all pass no problem.

Edit 2: Looks like there is mention of SafetyNet in the latest Canary Notes "Prevent SafetyNet from being removed from hide list". Maybe that will fix the issue.

Edit 3: Canary is a no go. Works for a bit when freshly installed but it seems like it is eventually detected by some combination of Google Play Services and Google Pay. Granted "Device is Certified" in the Play Store still.
[Magisk] jcmm11:
According to that error your boot image has already been patched by a different root program
[Magisk] martyfender:
The last time I had that message, in the last week on one device, I had to use the magisk uninstaller, followed by flashing the newer magisk.zip. Your results may vary though.
[Magisk] ashyx:
You need a clean unpatched boot image.

If you haven't used anything previously to patch the boot image then maybe it was pre-patched by your rom builder.

If that is the case then you need to have a word with the dev and tell them to refrain from this practice.

It is no longer the done thing to pre-root roms as it causes issues.