Magisk General Support / Discussion

Search This thread
By:
Advanced…
Didgeridoohan

Didgeridoohan

Retired Senior Moderator
May 31, 2012
12,300
1
14,850
Gone
Google Nexus 4
Nexus 6
jonners59 said:
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.
Click to expand...
Click to collapse

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.
 
  • Like
Reactions: ipdev and mazen1966
F

Faithful4real

Member
May 12, 2018
22
3
kotuamoalt said:
jonners59 said:
It absolutely makes sense. It is a concise, accurate description of the process needed to rollback magisk to an earlier version. I am sticking with 17.3 until 18.2 comes out. Supposedly, that will have all the fixes in it.

---------- Post added at 01:32 PM ---------- Previous post was at 01:10 PM ----------


If you expect to get help, you are going to have to provide more information than zero information.
What device are you using? What operating system are you using? Log files? Magisk version?
Help us help you.
Click to expand...
Click to collapse
Phone itel 1516plus
Android version 5.1
Magisk manager version is 7.0
Magisk version is 18.1
Click to expand...
Click to collapse
 

Attachments

  • magisk_log_20190320_060341.log
    23.2 KB · Views: 11
Swierk

Swierk

Senior Member
May 25, 2011
118
17
yung40oz84 said:
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
Click to expand...
Click to collapse


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
 
M

Marcondes BR

Member
Aug 23, 2014
36
8
Rio de Janeiro
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
 

Attachments

  • Screenshot_20190315-173309.png
    Screenshot_20190315-173309.png
    91.8 KB · Views: 535
KaMyKaSii

KaMyKaSii

Senior Member
Feb 25, 2015
1,391
686
Marcondes BR said:
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
Click to expand...
Click to collapse

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
 
martyfender

martyfender

Senior Member
Mar 9, 2017
3,391
1,860
Indianapolis, IN
Faithful4real said:

Have you tried Magisk in core only mode? Enable it in Magisk Manager settings and reboot.
If that doesn't work you could run Magisk uninstaller in a custom recovery if it is available for you device then reflash Magisk also in the custom recovery, before rebooting.
If none of the above works, have you thought about trying the Canary build? If you try Canary, I recommend running the magisk uninstaller in the custom recovery, or if you don't have a custom recovery, pick the uninstall button in Magisk Manager first.
Click to expand...
Click to collapse
 
Nebrassy

Nebrassy

Recognized Developer
Sep 17, 2015
1,083
2,516
Lattakia
Poco F5 Pro / Redmi K60 (China)
jonners59 said:
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.
Click to expand...
Click to collapse
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
 
  • Like
Reactions: ipdev
J

jonners59

Senior Member
Oct 4, 2010
322
17
London
Nebrassy said:
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
Click to expand...
Click to collapse

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?
 
W

watchman759

Member
Feb 11, 2019
8
0
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?
 
Swierk

Swierk

Senior Member
May 25, 2011
118
17
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
 
Last edited by a moderator:
jcmm11

jcmm11

Recognized Contributor
Feb 10, 2012
3,589
3,614
Google Pixel 4a 5G
watchman759 said:
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?
Click to expand...
Click to collapse
1 - if you flash a stock (unrooted) boot image then yes, you will lose root.
2 - exact details depend on your phone and if you have a/b system partitions or not. See https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation but generally speaking if you have a/b partitions then you can "turn off" Magisk then turn it back on. If you don't then you can't - you'll have to reinstall Magisk after applying the OTA and rebooting. (Note, you can't successfully apply an over the air OTA if you've modified system or vendor in any way, including just mounting it rw. Custom kernels will also prevent over the air OTAs)
3 - I have no clue. A more detailed explanation of the issues you're having may be helpful.

Changing (only) the boot image will NOT erase any data.
 
  • Like
Reactions: watchman759
Javi22

Javi22

Senior Member
Feb 26, 2011
2,041
188
Madrid
So I also noticed Google pay is no longer working. But also not my other bank apps, is it coincidence?

Are they supposed to still working? Safety net passes but all my apps says phone is rooted


My problem is even if I uninstall magisk, I can not use them! Any help here?

Enviado desde mi Pixel 2 XL mediante Tapatalk
 
garylawwd

garylawwd

Forum Moderator
Staff member
Aug 25, 2017
3,399
2,642
32
Cork
Samsung Galaxy Tab 3 10.1
Amazon Fire HD 8 and HD 10
Javi22 said:
So I also noticed Google pay is no longer working. But also not my other bank apps, is it coincidence?

Are they supposed to still working? Safety net passes but all my apps says phone is rooted


My problem is even if I uninstall magisk, I can not use them! Any help here?

Enviado desde mi Pixel 2 XL mediante Tapatalk
Click to expand...
Click to collapse
2000 posts? You should know better brother https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703/page46
 
Last edited:
  • Like
Reactions: Javi22
M

Mixedability

Member
Mar 1, 2019
5
1
Nottingham
www.whitelightphotography.co.uk
KaMyKaSii said:
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?
Click to expand...
Click to collapse

Yes, I've tried this endlessly...it may well be a timing issue, but the endless lack of success tells me it can't be done now. It has a small hole marked 'reset' which I can poke and it switches off. But just quickly touching the power button brings it straight to life as if it were just sleeping rather than rebooting.
If I were to disconnect the battery would this put it into a different state? One that I could work with?

Is it possible that with an unlocked bootloader and having only flashed the boot.img, I may actually not have any recovery to go to anyway? I had wiped user data and cache before flashing only the boot.img. I feel a knob for being negligent but I need to know what, if anything, I can now do...
 
K

kotuamoalt

Senior Member
Jun 23, 2016
210
58
OnePlus 8 Pro
Mixedability said:
Yes, I've tried this endlessly...it may well be a timing issue, but the endless lack of success tells me it can't be done now. It has a small hole marked 'reset' which I can poke and it switches off. But just quickly touching the power button brings it straight to life as if it were just sleeping rather than rebooting.
If I were to disconnect the battery would this put it into a different state? One that I could work with?

Is it possible that with an unlocked bootloader and having only flashed the boot.img, I may actually not have any recovery to go to anyway? I had wiped user data and cache before flashing only the boot.img. I feel a knob for being negligent but I need to know what, if anything, I can now do...
Click to expand...
Click to collapse
Have you tried holding the reset button for a longer amount of time? Say, 15 to 30 seconds?
 
Last edited:
You must log in or register to reply here.

Similar threads

T
  • Locked
  • Sticky
Magisk - The Magic Mask for Android
Replies
56
Views
6M
T
topjohnwu
T
  • Locked
[CLOSED][BETA][2018.7.19] Magisk v16.7 (1671)
Replies
7K
Views
3M
T
topjohnwu
Heisenberg
[Discussion] PokeMon Go Magisk Discussion Thread
Replies
5K
Views
649K
beneditodragon
beneditodragon
Didgeridoohan
[Discussion] Google Pay Magisk Discussion Thread
Replies
3K
Views
571K
I
ihavenolifee
yochananmarqos
Collection of Magisk Modules v2
Replies
1K
Views
1M
あなたの
あなたの

Top Liked Posts

24 Hours 30 Days All time
  • 2
    P
    pndwal
    J.Michael said:
    Is EMEI IMEI in another language?

    Please explain "as long as EMEI".

    I can't keep track of your situation. The ROM IDs you posted a week ago do not make it obvious that your device has anything with version 17 while you are trying to install version 16.

    I do not understand the country codes. Or the CSC, if that is something other than country code.

    Maybe you still aren't trying to install the right ROM. Remember, at this point we don't care what software you wish you had. You are supposed to be finding a ROM that is meant for your device, maybe associated with your carrier, maybe tagged with your location. Possibly complicated by it cannot be older than what is already on your device.

    Can you go to your service provider and tell them you need help? (If you bought the phone from someone other than your service provider, start with the person who sold you the phone.) The service provider should have some interest in helping you -- if you can't use the service, you won't keep paying for it.

    Maybe you can install a custom ROM. Check other threads to see whether something like LineageOS has been installed on the same device, and whether the device then functions as a phone.
    Click to expand...
    Click to collapse
    Other saga details:
    https://xdaforums.com/t/sm-g975f-is-this-the-end-of-the-journey-for-my-phone.4663849/#post-89440576

    👀 PW
    View
    1
    P
    pndwal
    Radzią said:
    Unfortunately, multi-user mode did not help. Deleting files from a folder adb Neither. I guess the only thing left is wipe data
    Click to expand...
    Click to collapse
    Mmm. Not sure that will help either... You can open a GitHub issue if you're prepared to install Debug Magisk build and supply logs; Devs might help further. 🙃 PW
    View
  • 5
    Lughnasadh
    Lughnasadh
    HippoMan said:
    I'm now having a problem hiding the TJW Magisk 27002 app ...

    I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.

    The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:

    (1) Unhide Magisk
    (2) Update Magisk (27002 was listed)
    (3) After Magisk manager restarted, I did Direct Update to 27002, including reboot
    (4) Magisk 27002 indeed came up properly after reboot.
    (5) Tried to perform Hide The Magisk App.

    I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.

    I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.

    I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.

    What am I missing?
    Click to expand...
    Click to collapse
    Known issue. A fix has been merged. You can use the Debug app, revert back to 27001 or wait until 27003 is released.

    EDIT: Ninja'd 🙃
    View
    4
    zgfg
    zgfg
    Jaitsu said:
    Is the Magisk 27001 APK/zip still available anywhere? I'd like to downgrade, but I can only find 27000 on Github and 27002 via update. I don't want to go to Canary in case the mounting changes break anything, or Debug as I hear the extra logging etc. causes performance issues (correct me if I'm wrong).
    Click to expand...
    Click to collapse
    Only v27000 is Stable. (and Beta). v27001 and v27002 are Canary or Debug

    Set your Update Channel to Stable and you will see (just like you can see also on GitHub) that latest Stable is v27000, there was never Stable v27001 or v27002

    Generally, Stable is always Nx100

    So, you cannot downgrade to Stable v27001 but Canary v27001 should be just like Stable v27000 (same codebase). That's also the general policy, whenever Nx100 Stable is released, then immediately comes Canary Nx100 +1, on the same code-base

    Therefore, downgrade to Stable v27000 instead
    View
    4
    Nergal di Cuthah
    Nergal di Cuthah
    sawdoctor said:
    Not sure if the fix has been pushed yet but looking at GitHub it's been sorted
    Click to expand...
    Click to collapse
    Not pushed yet according to my magisk app.
    Luckily i don't hide or need to hide; this is a sad bug and i hope, for others' sake, it's pushed as soon as the developers can. But that's also why it's canary and not beta or release, it's why (or should be why) we use canary, to squash bugs before the rest experience them.
    View
    4
    P
    pndwal
    sawdoctor said:
    Not sure if the fix has been pushed yet but looking at GitHub it's been sorted
    Click to expand...
    Click to collapse
    Not pushed yet... Looks like recent Android Gradle plugin upgrade just didn't build properly... Guess a new build may come once Upgrade AGP is reverted but may not happen till AGP upgrade is redone. 🤪 PW
    View
    4
    bombadier
    bombadier
    HippoMan said:
    I'm now having a problem hiding the TJW Magisk 27002 app ...

    I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.

    The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:

    (1) Unhide Magisk
    (2) Update Magisk (27002 was listed)
    (3) After Magisk manager restarted, I did Direct Update to 27002, including reboot
    (4) Magisk 27002 indeed came up properly after reboot.
    (5) Tried to perform Hide The Magisk App.

    I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.

    I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.

    I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.

    What am I missing?
    Click to expand...
    Click to collapse
    Known problem with 27002, the debug version doesn't have the problem with hiding, read back to see the discussion about it
    View
  • 1103
    T
    topjohnwu
    This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
    All information, including troubleshoot guides and notes, are in the Announcement Thread
    View
    156
    T
    topjohnwu
    Hello, I haven't given much support on XDA lately. It can be resulted from
    • University started and I have limited free time. In fact, I mostly develop during midnight
    • I live in Taiwan, which has large time zone differences between my European/American contributors/testers, which usually forces me to stay up late at night to discuss/test stuffs.
    • The new version is about to come, I don't want to spend effort on supporting old releases
    The planned update is delayed again and again, to some point I think I'll shed some light about what has been happening lately, also along with some announcements.

    New Forum!
    As you might have already discovered, Magisk got its own subforum on XDA! Many thanks to all the support you gave me, and much more information/features/support is about to come!
    **For developers supporting all the devices that are not using standard Android boot format, feel free to create threads in this section (actually, PLEASE do so) for your favorite devices after v7 is out. As I currently know, Asus devices require signing the boot image before flashing, and is model dependant; Sony devices seems to use ELF kernel that is unpatchable, or some has two ramdisks (inner + outer), both requires different workarounds; LG bootloader locked devices has to manually "BUMP" the boot image after flashing Magisk..... and there may be lots of other crazy boot image formats that haven't come up to my attention yet.
    It is impossible for me to support all these non-standard boot images, and I hope the community can collaborate to make Magisk running across all the devices. Overall, community collaboration is what XDA about :D

    The Pixel Phone
    Some of you might already know this news, that the next Pixel Phone right around the corner seems like it does not have ramdisk in boot image, which pretty much wrecked Magisk in all ways. However, it pretty much doomed root itself too. Kernel modifications is inevitable IMO, so I'll try to migrate my scripts to C programs that could possibly be included into the kernel itself. Note that I'm not familiar with linux kernel, I'm not even sure if my idea and concept is correct or not. But once the device is available, I think developers will find a way to bypass all the difficulties, and I'll do my best to learn things ;)

    Current Progress
    In the past month, I've spent quite some time learning SELinux, so that I can avoid using SuperSU's sepolicy patches. Thanks to the helps and tips from @phhusson and @Chainfire, I finally have a much clearer understanding of how SELinux works. The Magisk core parts (the scripts, boot image patches, new features, more supports) are actually done some time ago. What is causing all the delays is the Magisk Manager.
    To be completely honest, although I can code in Java without much issues, Magisk Manager is actually my first Android application, I had to reach out for assistance, and fortunately awesome developers like @DVDandroid and @digitalhigh contributed a lot, which makes the current Manager awesome.
    After the repo system and module management is mostly done, I was about to do some adjustments and release, but what we really done is decided to add another feature: auto-unroot with per-app settings. I decided to wait for it to be finished, and then do my adjustments. Due to reasons that'll be mentioned later, this feature will likely not be available for the next release (should come in future updates)

    Safety Net Disaster
    Those who are using Magisk for Safety Net bypass purposes must have known that Google recently updated the detection method of my Systemless Xposed. I still have no idea what Safety Net is detecting, so currently I cannot fix it on my side (also because I'm busy working on the next update). However, suhide developed by @Chainfire is able to hide Xposed and worked fine.
    However, only my Systemless Xposed v86.2, which is based on SuperSU's su.d, is supported using that method. v86.2 and v86.5 (latest, Magisk based) have nearly identical binaries, and the only difference is the path where the binaries are stored.
    I'm still not sure what's the real issue for it not being supported, I just hope it is not done intentionally.

    Conclusion
    Due to the fact that my Safety Net bypass is not 100% perfect now, I do not want to spend any more time waiting for auto-unroot to be polished. What I'm doing now is finishing up all the things I'd like to change in Magisk Manager (it has been a while since I last contributed to Manager, my fellow developers are doing all the heavy job), which might take a little more time, after that, packed with tons of information to be announced in Magisk Section, I'll release the long awaited update.

    Hope this lengthy post gives you the idea of the whole situation, and again thanks for all your support!!
    View
    121
    Chainfire
    Chainfire
    Ah, some Chainfire bashing, I hope it is not too late for me to exercise additional villainy.

    First, let me make clear I have nothing against @topjohnwu, nor against Magisk. Magisk is an interesting project and it certainly displays @topjohnwu ingenuity and persistence. I don't doubt we will see more interesting things from his hands.

    -------------------------

    What has happened here is not all that dark and complicated, from either end. I returned from holidays, and someone pointed me at Magisk. My first thought: interesting!

    Among other things, the thread lists some issues with SuperSU, which in combination with the phrase The developer also requests users to not bug Chainfire with compatibility requests for SuperSU with Magisk from the portal article, raised my left eyebrow by nigh half an inch. The popular systemless xposed mod is apparently now based on it, and apparently it now no longer works with SuperSU, and apparently I'm not supposed to fix that, nor any of the other found issues. I found that a bit weird. So yes, I have told @topjohnwu that I was a bit surprised he was posting about issues with SuperSU without notifying me about them (I can't fix or help fix issues I'm not aware of, after all).

    He's also spreading a modified version of the SuperSU package, which is not all that uncommon, nor necessarily a problem. I have not looked into what he modified, I only ran a few quick tests on one of my devices, and found some commonly used commands run as root to be broken. I have informed him of this as well.

    It appears the tool of choice for Magisk is phh's Superuser, because of some of the mentioned issues with SuperSU. That's fine by itself, but fixing issues in that superuser by incorporating SuperSU's binaries into it is a somewhat questionable practise. After all, SuperSU is a commercial closed-source package that helps pay for my dinner, and superuser is a direct competitor. I have informed him that I was surprised he did this without asking for permission. I have expressed similar surprise on him spreading a modified version of LiveBoot (which helps pay for a snack now and then).
    @topjohnwu has also stated that Magisk's scripts are largely influenced by mine (I have not checked). Scripts based on mine are used all over the place on XDA, some people have crafted amazing things based on them, I have never made an issue of this (otherwise I would have just made them binaries). But yes, I have also stated to him that I don't think it's very nice to base something on one program, and then using that to (almost exclusively) push something directly competing with that program.

    tl;dr Towards @topjohnwu, I have:
    - expressed surprise he has issues getting Magisk to work with SuperSU, and has chosen not to inform me about those
    - expressed surprise he is using SuperSU binaries in a competing superuser without permission
    - expressed surprise he is posting a modified LiveBoot without permission
    - informed him of issues with the modified SuperSU he has posted
    - let him know I thought it wasn't very nice to be applying my scripts to benefit seemingly exclusively that same competing superuser

    To be crystal clear:
    - I have not asked for an apology
    - I have not asked for Magisk to be abandoned, neither the root hiding nor systemless module parts, and certainly not systemless xposed
    - I have not made an issue of any of this anywhere, until this post
    - I have not even specifically asked for anything to be taken down (though obviously in my opinion the other superuser package mixed with SuperSU's binaries, as well as the LiveBoot package, should go)
    - I have not reported this thread to XDA moderators for copyright violations or otherwise

    While my conversation with @topjohnwu may not win any awards for being friendly (though it may win some for brevity), I think all things considered my response has been rather mild. To be perfectly honest, until the apology post, I thought this was over with already. I think the apology post was triggered because I haven't replied to his last PM for a while - I was in the zone, it happens.

    To emphasize again, I have nothing against @topjohnwu, Magisk, or systemless xposed, and it is certainly not my goal to see any of them go. If it can be made to work together with SuperSU, great.

    I get it though: you think of something, you want to see if you can make it work, you finally get it to work, you publish it, it takes off - enthusiasm gets the better of you. Maybe in the rush some mistakes are made. That doesn't mean you have to just drop it and run. None of my stuff would make it past 0.1 if I stopped at the first big mistake :)

    Aside from said being in the zone coding, I usually regret actually responding to these sort of things the day after, which has made me hesitant to reply. Surprise me.
    View
    76
    nathanchance
    nathanchance
    Thread temporarily closed so everyone sees this.

    The flood of "SafetyNet isn't working for me either!" posts are not helpful, at all. Please refrain from posting further, it will be looked into. Please do not forget that not passing SafetyNet is 100% NORMAL AND INTENDED when you have an unlocked booloader or running custom firmware. These are workarounds and they will be worked around in turn.

    The Flash
    Forum Moderator

    EDIT: Thread is reopened... I will be cleaning any SafetyNet posts for a while to keep the thread clean for real issues.
    View
    75
    T
    topjohnwu
    Hello everyone!

    I am aware that Google has updated Safety Net that makes Magisk itself a no go for Android Pay. In fact, I witnessed the change live while I am developing the new magiskhide, which should hide all Magisk modules and Magisk installed root.

    Google is serious about Safety Net now, clearly hunting down all possibility to run Xposed with Safety Net passed. I spend quite some time examining the new security measures last midnight, and fortunately it seems that it is possible to run Magisk and root along with Safety Net if no Xposed is running. I'm glad I removed the old root toggle at the right time lol, that is no longer feasible with the latest detection.

    So stay tuned for the next update, it will come with bug fixes, along with the new magiskhide to bypass that Safety Net.

    Google, how will a few systemless mods do any harm :p:p
    View

New posts