yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
That was solved for me by going to settings, apps, Magisk Manager, or Manager and deleting cache and data. You may have to reset some settings. When the app is launched again, it will download the proprietary code again when you check safetynet.

I have had this happen several times recently when updating Magisk.

If you are on the Canary build, you need the latest, Canary Magisk Manager, because the hard coded update links have been changed to point to the new download location.
[Magisk] arbajkhan1:
Ftt
[Magisk] Xperianer:
Might it be possible to use the techniques inside of LZplay app to get root access (install magisk) to P30pro?
[Magisk] chooks06:
You may want to read this article.. I've not validated it though..

https://9to5google.com/2019/10/01/h...l-google-apps-as-researcher-exposes-backdoor/
[Magisk] zputnyq:
Thank you, that's work :)
[Magisk] zgfg:
Yes, there are many articles alike today.

And indeed, htttp://www.lzplay.net is N/A anymore

IMO, lzplay was mainly signed with Huawei keys to be able to install Google Play Services as system service/app, whereas Magisk installation requires writing to Recovery partition
[Magisk] martyfender:
Lzplay was taken down.
[Magisk] Georgi_Ko:
Hello. My Magisk recently started failing the ctsprofile (it's set to false, basic integrity is set to true). No idea what happened. I even installed the Magisk Hide Props Config module using the Magisk app without any luck. I tried switching to Beta channel if Magisk to try 19.4 version(I was on 19.3) but that didn't help either. What else I can try to get it back working?
[Magisk] amogha*:
Yep Google has done something
[Magisk] martyfender:
Are you on a custom rom, instead of the stock? [MENTION=4470081]topjohnwu[/MENTION] has a twitter blog with info on what Google has changed, suddenly to cause custom roms to fail cts profile. A solution was not posted, however. You may be sol, for the time being. Or maybe I misunderstood what he stated.
[Magisk] Didgeridoohan:
In that case it's probably not the OEM battery optimising causing you issues, but if it happens after exiting deep sleep it still sounds like that is the issue. Worth experimenting...

Did you just install the module or did you also apply a certified fingerprint? You'll have to do that or the module won't actually do anything...

Custom ROMs have never been CTS certified (nothing new there). It's just that we've always been able to use certified device fingerprints to circumvent that. As far as I can tell, everything's still working as normal on that front (except for Huawei). Remains to be seen what further checks (if any) Google will add as a result of this though...
[Magisk] martyfender:
Thanks for clarifying that. The way it was written made me think he was talking about custom roms, in general.
[Magisk] rastawobler:
Enyone who can help me getting magic . Ones it stay for I little while then back to basics . I'm one a asus_X00PD :angel:
[Magisk] ashyx:
I suggest posting in your own language too. Someone may be able to understand you. The translation isn't the best.
[Magisk] Georgi_Ko:
The CTS profile check was failing before I updated my Magisk from 19.3 to 19.4. I did that simple to check if updating to 19.4 will fix the issue and make the check to pass
[Magisk] gkillerx:
Android pay works! I'm a bit shocked though that horizon go (TV app) doesn't work it still sees xposed lol (using system less xposed and system less super user (the ss version)

Running Android 6 stock oneplus 3 ram.
[Magisk] adrman:
Magisk in its current implementation passes both the Playground Test and Safetynet Helper. However, payments do not work.
[Magisk] mahmutuslu:
samsung galaxy s7 edge g935f dont work
[Magisk] Portgas D. Ace:
http://xdaforums.com/showpost.php?p=68050672&postcount=161
[Magisk] bobby janow:
Would there be any way, at least until twrp is updated for N encrypted, to flash this? It seems not because the only way to flash a zip now would be with Flashfire (stock recovery naturally) and that requires root privileges. Kind of a catch 22 no?

Sorry, n5x. I don't think the 6p has this problem.
[Magisk] steveo17:
with the 6p at least, you can use TWRP 3.0.0 and then load ADB sideload and flash from the computer
[Magisk] bobby janow:
Was told I couldn't do that with 5x. Can't decrypt.
[Magisk] steveo17:
its not going to decrypt. thats why you need to ADB sideload
[Magisk] anantharam:
How exactly do we do that?

I am stuck in a boot loop now after installing Magisk, apparently it doesn't support my phone, I am able to log into TWRP and use the file manager, I renamed /data/magisk.img to something else and I removed .gz from /data/stock_boot[md5].img.gz but my phone is still not booting up. I do not see any log files generated in /cache or in /dev/log from inside the TWRP file manager.

I am not sure how to proceed now...

The device is am using is Lenovo Vibe X3 (X3a40) using the stock Marshmallow ROM with Vibe UI.​
[Magisk] KaMyKaSii:
It is not simply remove the extension in the file name. Copy the file to your computer, extract with 7-zip, copy the extracted img back to the phone and flash with TWRP on boot partition
[Magisk] anantharam:
But how do I copy the file to my system if my phone is not booting up? My system doesn't seem to recognize my phone via adb when it is in recovery mode. I always get adb devices as empty...
[Magisk] RandomPooka:
Now that makes sense. Beautiful. I'm not sure what sort of mental block I was having, but I couldn't put the two together. Thanks
[Magisk] kirby2ig:
The next step would be to flash the boot.img. To do this, go to "Install" menu in TRWP and change to image mode by hitting the "Install Image" button in the bottom right. Then you will need to navigate to the boot.img file and select it. TWRP will ask you if it is a boot or a recovery image. When that happens, select boot. Then flash it and you will be good to go.

But before flashing, make sure you actually decompress the file. I am not sure by your post whether or not you decompressed it properly or just removed the .gz on the end.

If you have not decompressed it properly, first put the .gz back on the end. Then, activate MTP in TWRP and copy the file over to your computer. Decompress it there and send it back to the phone so you can flash it.

If this doesn't work, you can try downloading the stock boot.img for your device and flash that in TWRP using the same process.

Good luck fixing your phone!
[Magisk] KaMyKaSii:
Are you sure you install the drivers needed to run adb? And you can also copy the file to memory card and place in computer with some adapter
[Magisk] anantharam:
I restored the boot image and now my phone won't even boot into recovery! :(

Any other ideas?

All the adb commands used to work without any issues before I tried Magisk, so I don't think drivers would be the issue. I finally ended up copying the boot image from TWRP to sd card and then copying it to system via USB cable. But now after restoring the old boot image, I lost access to recovery too, pressing both the volume buttons while pressing the power button does nothing now... :crying:
[Magisk] kirby2ig:
Sounds like you will have to flash stock images with fastboot.

EDIT: You could try flashing TWRP again in fastboot like you did in the beginning. Also, can you upload that boot.img.gz file somewhere so we can take a look at it if it is still on your computer?
[Magisk] Jacob_K:
Can confirm I got it to work today. Restored dpi to stock, unmounted via magisk, paid with android pay and it went through.
[Magisk] anantharam:
Yup, finally I flashed my Stock image in EDL mode.

So now the question is what should I submit in my bug report to Magisk if I didn't get any log files generated in /cache?

I am ready to try this even one more time but I am not sure how I can take log files during the bootup process. I see in the first post something about using PCs to get the logs during bootup, do you know how I can do that?
[Magisk] kirby2ig:
I am not sure how to get a log when the phone can't boot up either. Maybe the OP can help.
[Magisk] anantharam:
Here is the boot.img.gz file that was generated in /data is : http://www.filedropper.com/stockboot712a55a9740546a1c5d61fe33e007eb2img

And here is the magisk.img file that was generated in /data is : http://www.filedropper.com/magisk

No Log files were generated in /cache or in /dev/log, the device is Lenovo Vibe X3(Model Number X3a40).

Not sure what else I can provide to debug my issue, but let me know if I can do anything else. This is stock Vibe UI ROM from Lenovo, so I guess Lenovo must have heavily modified it like Samsung does to their TouchWiz and that caused Magisk to break...
[Magisk] EViollet:
? it's too early. I read too fast. Sorry about that.;)

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
[Magisk] MrPerson:
Anyone else have issues with using Android Pay in apps (such as NewEgg) for purchases? I have Magisk, phh's root, and systemless xposed installed on my OnePlus One running SultanXDA's CM13 (6.0.1).

Toggling root off allowed me to finally get into the Android Pay app far enough to connect my credit card, but I haven't been able to use it to pay in apps at all. Haven't had a chance to use it in person, but in app use was the main reason I wanted to use Android Pay. Any ideas what the problem could be?

I've made sure to uninstall the old xposed and install systemless (then uninstalled systemless and reinstalled systemless again), I'm on the latest version of Magisk and phh's root, I've triple checked that root is toggled off when trying to make payments, etc.

Also, I can't log in to Pokemon Go, so I believe that it is still seeing that I'm rooted as well. So it seems that the toggle isn't working, I guess. I'm really stumped.

Edit: Looks like the problem must be systemless xposed, according to some recent posts. Guess I'll be looking for Chainfire's suhide.

Edit 2: I tried uninstalled systemless xposed just to see if that is actually the problem. Uninstalling did not fix anything, unless I literally have to uninstall all parts of xposed (modules/framework UI/etc). I flashed the uninstaller and then when it booted back up and tried to use Android Pay or Pokemon Go, no luck. Any ideas?
[Magisk] topjohnwu:
It had been a long wait guys :)

Finally, the Manager is pretty much done.

Constructing threads for new info and doing some final last minute checks should take a little more time, but expect the update to drop today!!
[Magisk] mathy007:
What's the command line code exactly? FYI am using HTC one M7 dual sim running lollipop 5.0.2
[Magisk] TheSpaceManatee:
I have the exact same problem as you except im on cm13. Hope u fix it and teach me how to :p
[Magisk] Rayman96:
Everything is written. You need to look more careful.
[Magisk] 3Shirts:
Sorry, I did hunt through this thread but it's become a bit of a cluster**** with all the 'help me fix pokemon' posts so I missed that. Thanks.
[Magisk] utbf:
Thanks for your answer!

Unfortunately I am not good enough to understand which would be the best way to fix this. I will ask in the sony threads of this forum for more suggestions and will get more informations before i try something.
[Magisk] Artim_96:
Well, you only Ned to find a was to Flash Advanced Kernel, which should be found in your devices thread.
[Magisk] mathy007:
could you please tell me what exactly what i need to do?
[Magisk] Biges:
Thanks. Seems like things are getting more and more complicated. I'll try to emulate your route.

I'v also found this, looks interesting, understandable instructions even for a dummy like me :D

https://www.reddit.com/r/pokemongodev/comments/53ood1/migrate_from_magisk_phhs_superuser_xposed/
[Magisk] ditchmagnet:
Can anyone get magisk viper4android working on Nexus 6 6.0.1? I can't get it to work on mine.
[Magisk] cubandanger05:
Yes, it's the 86.2 version you must use. You can't use phh's superuser, you have to go systemless SuperSU, and suhide 53

---------- Post added at 01:49 PM ---------- Previous post was at 01:47 PM ----------

Yes, I followed that guys guide myself, I just didn't have to do the commands in twrp bcz my rom supported systemless root and installed SuperSU 2.78 systemlessly automatically
[Magisk] kingsven149:
Hello does someone have the Stock Kernel for the sgs5 Android 6?
[Magisk] Krunk_Kracker:
Maybe I'm an idiot, but I cannot get this working for the life of me. I've tried it on both PureNexus and SlimRom roms on my Nexus 6p, I've followed all directions and still nothing. It says within the Magisk manager app that it Not Rooted, and is enforcing, when in fact it is rooted with phh's supersu per the instructions. I'm lost as to what the issue might be. I can't toggle within the manager app and it never asks for root privileges.
[Magisk] LeeDroid:
Try reflashing phh supersu and make sure the phh SuperUser app is installed
[Magisk] Krunk_Kracker:
Turns out, I think I am an idiot. I wasn't using the -17 version of phh's supersu, I picked up his standard zip somewhere along the line I think. About to try it again.
[Magisk] LeeDroid:
Make sure you remove it first & suggest your ROM dev offers a no root installation option;)
[Magisk] Krunk_Kracker:
Turns out, all my troubles were the standard phh supersu.zip I found somewhere. After I used the -17 supersu zip, it's working as intended. I'll make a post for with the dev of purenexus. Thanks for all your help!
[Magisk] BrahmaGandhi:
looks like others has the same issue with cts failed suddenly,

well, same here. I'm on Xtended pie, OP3T, magisk 19.3 MM 7.3.2. started to failing cts since today although basic integrity stays true. downgrade to magisk 19.2 and or up to 19.4 doesn't help either. is this due play services update? any workaround for this? beside...waiting.

thank you
[Magisk] Georgi_Ko:
I just installed the module, yes. Could you please let me know how to apply a "certified fingerprint"? Thank you in advance
[Magisk] martyfender:
MagiskHide Props Config documentation:

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md

Also the threads OP (Opening Page), give a great overview of the module:

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228
[Magisk] Didgeridoohan:
What's the values for ro.build.fingerprint and ro.build.version.security_patch on that ROM? I have no issues passing CTS on my OP3T with ArrowOS, as long as I set a certified fingerprint.

Basically, run the command "props" in a terminal and then follow the menu's/instructions.

You'll find all the info you need in the module docs:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md

The module thread is also a good resource:

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228
[Magisk] palmbeach05:
Idk if its an added factor or just an irrelevant factor to the process, but i resolved the play store certified device issue first before resolving the cts issue using the method you're referencing.
[Magisk] Georgi_Ko:
Thank you very much, will give that a try :)
[Magisk] Didgeridoohan:
Passing SafetyNet and having the Play store reporting certified are both tied to CTS, so they are very much related.
[Magisk] BrahmaGandhi:
ro.build.fingerprint=OnePlus/OnePlus3/OnePlus3:9/PKQ1.181203.001/1905251415:user/release-keys

ro.build.version.security_patch=2019-09-05

it was all good without certified fingerprint, was able to passed all checks.. so why become problem now?

*btw just noticed the play store currently also says "device not certified"

if i follow the ceritifying fingerprint guide, any guarantee it will works? thank you

---------- Post added at 23:22 ---------- Previous post was at 23:08 ----------

i found one in MM''s module download section :

Name: MagiskProps Hide Config

version/date: v4.0.3-v63 / sept, 5th

should i flash this module, then running terminal emulator?

and next what specific commands should i type.. im noob on doing commands thing. thanks for your help
[Magisk] sunbinyuan:
CtsProfile was failing for me then I updated to magisk 19.4 but it was still failing. After installing props config and setting to the original phones signature, the cts passed again.
[Magisk] TheXclusive814:
post can be deleted
[Magisk] Didgeridoohan:
That looks like an old OP3 fingerprint. It would likely not be able to pass CTS with a security patch date for september. Did your ROM recently update the security patch?

Play Store certification is directy linked to CTS, so if you fail that your device will become uncertified.

That's my module... The command you want is "props", then follow the on-screen menus and instructions ("Edit device fingerprint" - "Pick a certified fingerprint" and then pick the device/print you want). More info in the module's thread and docs.
[Magisk] BrahmaGandhi:
module downloaded, rebooted twice, when type su on terminal emu. it says "su not found" i couldnt get su access, so i cant use "props" command. although the terminal emu app is already granted in MM's superuser section. its weird. when i enabled magisk only core, then re-type su access is granted.

busybox osmosis already installed.

what i missed here?

may i know your current magisk and MM version on your op3t, sir?

*oh and if you wondering why i didn't update the magisk version, it's because i have issue with root access in magisk 19.4 (can't write/delete files/folders onto root dir.)

**attach SS for my current magisk status, modules, terminal emu. thanks for your help

Edit: for your Q' regarding ROM's sec patch..

it was all fine before today. anyways, MSM-Xtended ROM latest build was sept, 15th. fingerprint build based on build.prop and also sec. patch date was 2019-09-05
[Magisk] Georgi_Ko:
That worked! Thank you very much!
[Magisk] BrahmaGandhi:
update: ok to restore root access etc so i took long steps....

re-flashed stock boot image

installed magisk (19.3 , 7.3.4)

force closed+wiped play store

root access OK (su granted)

flashed busybox

flashed your module (running command, etc, done)

safetynet check both TRUE

play store check "device is certified"

.......

re-install the rest of all the modules

reboot and re-check safetynet, both stays TRUE

pffffhh,,,this google safetynet thingies could really such pain in the a*s sometime! uh huh that's google!

Thanks for the help and your time and your module of course ? thanks again
[Magisk] oms_muc:
19.3, 19.4 won't boot on mi8

THX for helping me. Sadly I seem to be the only one effected with such a popular device.

- I did take a look at topjohnwu instructions and dindt find any obvious resolution for my device that differs from what is available on youtube.

- I dindt try 19.5.

- I believe not having an a/b device due to the following output of "nothing":

C:\Users\olive\adb-fastboot\platform-tools>adb shell

dipper:/ $

dipper:/ $ getprop ro.build.ab_update

dipper:/ $ getprop ro.build.system_root_image

dipper:/ $

- Regarding privious installed Magisk stuff: Hence I bought this device 2nd hand and it was unlocked, I was unsure and wiped it fully with TWRP and reinstalled MIUI 10.3.5 Global ROM.

-I have saved the requested logs for further investigations: httppppps://1drv.ms/u/s!Ak2fFOX7cX_wmdIHKmAEmShs3TGWgQ?e=dezgge

I guess I'll give up with this Stock ROM and try to install a custom one, hoping I than can install magisk.

BTW: The reason why I believe needing ROOT is that I need to change the colors (theme) of apps such as Whatsapp and found only Substratum, which needs root access. This is for my mother which has an eye disease and best needs always a dark theme with white text in order to use an android phone, like her Windows Mobile Phone today.
[Magisk] martyfender:
I have closed out the tab I had open for your device specs, but if I recall correctly, it originally came with Android 8.1. If a custom rom doesn't help, maybe going back to and older Android version would help, however, I am not sure at this point. Before doing so, you could try Canary 19.5.
[Magisk] ArmynC:
How I can solve the Google apps (and some other apps) crash bug? It has to do with cts? If I try to check SafetyNet it doesn't work either (infinte time check).
[Magisk] BJHiltbrand:
Jack In The Box Mobile app still detecting root

Hi, I have not been able to open the Jack In The Box app on my phone for the last 6 months or so. Even though I have Magisk marked as hidden for the app, it still crashes immediately upon opening, indicating that it is still detecting root on my device. I still pass safetynet checks and I don't have an issue with any other app but this one. Does anyone know how to figure out what method the app is using to detect root, and why Magisk isn't able to hide? Thanks.
[Magisk] guest4711:
Did you try to hide MagiskManager itself by repackaging it to random package name? Some apps simply search for "MagiskManager".

If this does not help, have a look at [MENTION=4667597]Didgeridoohan[/MENTION]'s fine manual/faq: https://www.didgeridoohan.com/magisk/MagiskHide

---

For those having problems installing modules cause of option error in unzip like this

- Copying zip to temp directory
- Installing YouTube_Vanced_-_Magisk_Repo-v14.21.54(b01.40.20)(25).zip
unzip: invalid option -- j
usage: unzip [-d DIR] [-lnopqv] ZIP [FILE...] [-x FILE...]
! Unable to extract zip file!
! Installation failed

here's my workaround:

1. delete the folder /sbin/.magisk/busybox

2. reboot

3. install module

4. reboot and enjoy.

Explanation: On some devices magisk's internal busybox will not be installed (the rigth way, error is file is busy) so installer uses the standard unzip command which does not support -j option (ignore path). When deleting the busybox folder Magisk will create the directory and it's contents the right way, so unzip -j works until next reboot.

The problem with busybox will come again after next reboot but you'll notice if installing another module or version only.
[Magisk] Pilaster-99:
Hi!

I have used magisk combined with a system app uninstaller to successfully remove the playstore.

1.

I was told it would be a good idea to delete such a root app afterwards + download a root-check app - why is that exactly and do you recommend it as well?

2.

I downloaded the "root checker" by "free android tools" on another phone and then transferred it to the phone without the playstore. However it does not open there - probably bcs some apps incl this won't run without certain google features. Do you know of a root checker that can work on such a phone?

Thanks alot!
[Magisk] Ch3vr0n:
1. Magisk (uninstaller) cant remove any app but magisk itself. It can't modify system apps. So whatever you used to uninstall the google play store, it wasn't magisk.

2. Wrong topic, that's beyond the scope of the magisk topic. As to why it's crashing, perhaps because it's calling to the play store api for ads, licensing,... Either way, you're in the wrong topic for that
[Magisk] mbze430:
LG's SmartThinQ not working

It's been 3 or so Magisk updates but SmartThinQ app still say it can see the device is rooted.

Any fixes?
[Magisk] guest4711:
Did you try to hide MagiskManager itself by repackaging it to random package name? Some apps simply search for "MagiskManager".

If this does not help, have a look at [MENTION=4667597]Didgeridoohan[/MENTION]'s fine manual/faq: https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] mbze430:
If you are talking about the the one in Settings, then yes I have that enabled.
[Magisk] martyfender:
My best guess would be to factory reset or reinstall your rom. Make sure you backup important items first, though.

What is your device and Android. Version?
[Magisk] xXraprodyXx:
ctsprofile is failing when i do the safetynet test since yesterday, so i cant use google pay or anything like that. Was working perfectly til yesterday, I didnt update or change anything related to magisk. Im using a oneplus 5t on android 9. Tried magisk 19.3 and 19.4