yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Colour me curious: what part of what I wrote made you think about passing SafetyNet with Xposed? :crying:
[Magisk] martyfender:
You can't pass SafetyNet with Xposed installed.
[Magisk] demonoidmaster:
It wasn't anything you wrote, i had tried USNF way before you had commented but i saw that he talked about it and you did too and i just wanted to say about my results lol

But i only did it as a test (to then try login to snapchat while xposed on) which didn't work since sc relies on safety net and that even with USNF xposed still trips it

---------- Post added at 09:53 PM ---------- Previous post was at 09:49 PM ----------

I already know that, i didn't mean i tried this just now, i tried Universal Safetynet fixer yesterday while testing snapchat 10.26.5.0 along with snaptools and stuff, but i only commented now because yknow.. It's on topic since that other guy talked about it

---------- Post added at 09:55 PM ---------- Previous post was at 09:53 PM ----------

i know
[Magisk] Okahuma:
Issue installing Magisk

Hi! Any help is appreciated. Also, english is not my first language, so I apologize for anything that hurts your eyes.

My phone is the athene XT1640 (Moto G4 Plus).

I managed to get twrp working nicely and made a backup of the newly factory reset and freshly flashed to a stock ROM phone. Then I tried installing Magisk. First option was making a patched boot.img from the stock ROM I used, which seemed to work. Then I tried flashing said patched boot.img and had a failure (too many links).

>fastboot flash boot patched_boot.img

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:boot: not found

target reported max download size of 536870912 bytes

sending 'boot' (12048 KB)...

OKAY [ 0.400s]

writing 'boot'...

FAILED (status read failed (Too many links))

finished. total time: 0.559s

I tried finding a solution to this to no avail. I then tried installing the v16 Magisk.zip with twrp. This led to softbricking (I think?). Phone could not be turned on, even though I tried waiting for a long while. Black screen with a blinking white light (charging indicator). Had to restore the backup I made.

Here is the pastebin log from twrp of this last try I just made: pastebin.com/DKcjBmcU

Thanks for any insights!
[Magisk] jcmm11:
For starters the pastebin log is saying that the boot image was already patched

"Magisk patched image detected"

Reflash a stock boot image and try again (via TWRP). Although if you already did a full restore you probably are already back on stock.
[Magisk] Adhil Rahman:
I am on latest magisk beta 16.3 and i get this message tried both via app and twrp even tried uninstalling and installing again. Any fix?
[Magisk] Okahuma:
Flashed a stock ROM again. Tried through twrp with Magisk beta v16.3. Same failure. Black screen with blinking charging indicator, no boot. Flashing just the boot.img from stock ROM enables boot, but no Magisk is installed it seems.

Log from this attempt (twrp): pastebin.com/xYzvwZk1

And then again with stable v16. Same result.

Log from this attempt (twrp, this one I cut out a large section (over 14k lines) that was making a backup before installing Magisk): pastebin.com/9Htbb3zL

I tried again with a fresh ROM doing the install through Magisk Manager and flashing the patched boot, but got the same "Too many links" error. If it's any indication of the issue, this is the only point in which the bootloader restarts, and right after it comes back the prompt gives the error.

Thanks for helping me out mate.
[Magisk] Didgeridoohan:
The fix is that the module creator need to update to the latest module template. Backwards compatibility has been removed in Magisk v16.3.

Quick search of "too many links", shows some success with trying different USB cables and switching USB ports, but other than that: nothing. Does it normally work flashing images with fastboot?

But, since you have TWRP, you don't really need to bother with fastboot. And the recovery log looks fine.

Things to try:

Flash the patched boot image with TWRP (change to "Image" instead of "Zip" on the Install screen).

Enable "Preserve dm-verity" and/or "forced encryption" when flashing/patching. Experiment with one or the other or both.

And if it fails you don't have to flash the whole ROM. The stock boot image is enough (through TWRP works).
[Magisk] Object0:
Yesterday I've received a notification about the new version of Magisk Manager, clicked "install", the installation process has started, there was a warning "Boot partition space insufficient" (it used to be before I guess). The phone went to reboot, but turned off instead (or just screen off?). I holded the power button, but the phone did not turn on, pressed a combo of buttons, the phone turned on and got into endless boot (got stuck on logo). I rebooted it with keys again and enter into TWRP, charge level was 68%. So decided to Wipe it, but after a few seconds the touch screen stopped responding so I couldn't. Tried twice, the same issue. Decided to reflash the firmware, turned the phone off via Power Off in TWRP, after that the phone stopped turning on (completely!). Does not react at all. Not charging, no leds, no vibro.. completely nothing. Seem to be hard bricked, don't understand why.

P.S. Samsung S7 Edge.
[Magisk] Didgeridoohan:
I'm assuming you also tried updating Magisk after updating the Manager. I'm also going to assume you didn't save the installation log before rebooting, correct?

I think you'd be better off trying to find help on how to recover in your device's forum.
[Magisk] Object0:
Didgeridoohan, yes, I did't save any logs. I just don't understand why it hard bricked / dead, just after updating Magisk Manager.
[Magisk] Didgeridoohan:
Just to clarify: did you first update the Manager and then Magisk (it's twofold) and was it when you updated Magisk that you saw this message? Magisk version? Stable or beta?
[Magisk] Object0:
Stable. The latest one on yesterday. The process before it's dead was like flashing Magisk module then reboot.

I guess it's dead on flashing Magisk, not Manager, but I am not 100% sure.
[Magisk] GeTex:
sounds like a dead emmc to me honestly, aboot should be protected, or corrupt partition area, either way head to your device forum
[Magisk] CrimsonBloodfang:
Is it just me or is the "Downloads" in Magisk Manager sometimes takes forever to load? I've wiped Dalvik/Art Cache and Cache from my TWRP so I know that did something.
[Magisk] guest4711:
"MagiskManager -- Settings -- Clear Repo Cache" should be sufficient...
[Magisk] Okahuma:
Thanks for the reply. I get the same error trying to install the patched_boot.img as trying to install the Magisk.zip. Instead of booting up, I only get a blinking white light from the phone after the install and reboot. Attempted patching with no options, with both and with each. Flashing the stock boot brings it back up (either through fastboot or twrp). Here is the log from an attempt with both options (cut a portion that was a backup): pastebin.com/ggWZ8GAr

The install from .img seems to be just a couple lines and doesn't throw any errors. I have no idea how to proceed. Is there anything I can do to get a more detailed log?

[IMAGE FLASH STARTED]

Image to flash: '/sdcard/Download/booto.img'

Calculating restore details...

I:Image filename is: booto.img

I:Reading '/sdcard/Download/booto.img', writing '/dev/block/mmcblk0p28'

[IMAGE FLASH COMPLETED]

Should I maybe try installing a custom Kernel?

Thanks for the help!

Edit: Yeah, it flashes other stuff no problem. The only file it throws that error at is the patched boot file.

Edit2: I don't know if this is relevant. I had hardbricked the phone and had to flash a feb2018 gpt.bin. So the phone has everything in NPJS25.93-14-10 except the gpt.bin.
[Magisk] GryphonBR:
I tried searching both on this thread and using Google but couldn't find an answer; is it possible to automate Magisk installation after a ROM update using /cache/recovery/command, by any chance? I already have to use this command to perform my update, and since afterwards I'd be without TWRP for a while, I'd prefer installing Magisk sooner rather than later (specially because, if Magisk's installed, I'd have the possibility to internally install TWRP afterwards).
[Magisk] BillGoss:
If you're using TWRP, you can use open recovery script to install your update and Magisk. That way you won't lose TWRP.

See

http://wiki.rootzwiki.com/OpenRecoveryScript

https://twrp.me/faq/openrecoveryscript.html

I've attached a sample of what my script looks like when I flash an update (LineageOS). The actual script file is /cache/recovery/openrecoveryscript

I had to add the ".txt" to attach it to this post.
[Magisk] mattakacas:
No Root After flashing updated_boot.img using Magisk Manager

I admit I am new to tinkering with this sort of thing so I could be missing something easy here. I got a new pixel 2 xl phone today (the carrier unlocked version). I let it run OS updates after i first turned it on. Its now running Android 8.1.0 with build OPM1.171019.021. I unlocked the bootloader by first of course enabling it within developer options within the android OS itself, then running the following fastboot commands:

fastboot flashing unlock

fastboot flashing unlock_critical

These appeared to work and I now get the nasty warning message when i reboot my phone that i shouldnt store anything sensitive on it. From there, I downloaded and installed Magisk Manager 5.6.3 and installed that APK on my phone. When i first ran it, it updated itself to 5.6.4 (112) (com.topjohnwvu.magisk). From there i downloaded the factory image straight from google that matched by current build, labeled '8.1.0 (OPM1.171019.021, Mar 2018)' on googles listing. I extracted the boot.img from within the factory image and transferred it to my pixel 2 xl via google drive. I then used Magisk Manager to patch the aforementioned boot.img. This seemed to complete just fine without any errors. Then I used adb to get the patched image file back to my PC by running:

adb pull /sdcard/MagiskManager/patched_boot.img

I then put my phone back into bootloader mode and ran the following command out of fastboot:

fastboot flash boot /path/to/patched_boot.img

This appeared to finish just fine with output that looked like:

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash boot patched_boot.img

target reported max download size of 536870912 bytes

sending 'boot_a' (25888 KB)...

OKAY [ 0.556s]

writing 'boot_a'...

OKAY [ 0.176s]

finished. total time: 0.733s

From there I rebooted by phone and checked magisk manager. It doesnt show that I have root. It shows me 2 check boxes at the top of the screen next to 'Latest Version v16.0' and 'Installed Version v16.0'. There is no mention of root at the top of the screen. Under advanced settings both options for preserve force encryption and preserve AVB 2.0/dm-verity are checked. Beneath that is a button that has the magisk icon with the text 'Install' in large font. I also have an uninstall button beneath that.

Clicking install seems to prompt me to patch a boot.img again so I seem to be stuck in a loop as far as trying to gain root. Can anyone suggest what I should do or tell me what i did wrong? Thanks in advance!
[Magisk] yochananmarqos:
I don't have a Pixel, however it sounds like you did everything right. From your description, Magisk Manager looks as it should. Do you have a Superuser option in the hamburger menu? Have you tried any root apps to see if you get a su prompt?
[Magisk] mattakacas:
Yes, u know what - apparently I did do everything right and it is working. I ran rootchecker, it prompted me for superuser, i granted it and it verified that I have root. Then I installer the tether enabler module (which I why I really wanted root in the first place) and its working now too. I guess i expected to see a green check mark next to something telling me I had root within magisk manager and I was surprised there was still an install button after I completed the install. I think i was looking at an old guide with an out of date screenshot of magisk manager or something.

In any case im good to go now, thanks for the quick reply, have a great weekend!
[Magisk] GryphonBR:
I'd use openrecovery, but this is a Huawei phone and pay off the update process requires me to flash an alternative recovery image in the first place. I'll give it a try, though, hopefully this works - thanks!
[Magisk] Sam Nakamura:
Thanks for this hint :highfive: this post did me a huge favor by clearing my personal misunderstanding with Magisk, somehow I wasn't able to draw the line, this solved my persisting issue with my mtk device, as for some reason the "patch boot image" function stopped working (probably a device specific issue) and all attempts to patch the boot.img on another device ended with bootloop when patched boot image is flashed... Finally I understood that this is because of a mismatch between ARM and ARM64, never thought of it to be relevant...
[Magisk] marius.podiuc:
Hi. I have Note8 on oreo custom RON by Dr. Ketan.

I have the latest Magisk 16.3 installed. I started getting mad, because it keep un installing itself. I cannot find any solution. On s8+ I din't have this problem. I have many apps which is required to be rooted. Is there any solving solution for this to keep the device rooted avoiding to keep going on recovery and flash again the Magisk zip file. Thanks a lot for your work. I really want to pay for the solutions.
[Magisk] facet_:
Welcome, I have a huge problem with Magisk, namely from version 15.2 upwards after installation everything works beautifully but I can't uninstall the application I want, trying to uninstall anything the phone goes into soft reboot. I tested version 14 and there everything is ok. I also tested beta 16.3 and the same problem. I would stay on version 14, but in this case I don't have a bank application but I can uninstall it all. I have no problem with installing magic units, either through the magisk manager or twrp. This banking application on every version starting from 15.2 works without any problems. Android N 7.0 phone to Huawei Honor Note 8.
[Magisk] jcmm11:
[MENTION=8005460]Guivre[/MENTION] [MENTION=365965]facet_[/MENTION]

Where are the
[Magisk] Guivre:
I've edited my TWRP log into my post. Matlog isn't working and I don't have a magisk log because it never loaded to begin with.
[Magisk] jhedfors:
Always attach logs, rather than include them in your post. It is very tedious to scroll past!

EDIT: If you can't attach, upload it somewhere, and post a link to it.
[Magisk] GradiusBR:
Magisk 16.0 fails on SafetyNet test on my Samsungu J5 Metal 2016, Android 6.0.1 with security patch February 2017. Anyone have an idea why SafetyNet fails or how to fix it?
[Magisk] Pkt_Lnt:
The person in this thread who bends over backward helping those who won't read or search has written a long, thorough guide. Here are links. :D :good:

https://www.didgeridoohan.com/magisk/HomePage

https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] facet_:
I'm sorry for my English but I do not understand what to write

Wysłane z mojego EDI-AL10 przy użyciu Tapatalka
[Magisk] BillGoss:
He was saying that you need to provide logs.
[Magisk] facet_:
clear, but from what software, from the bank application with magisk 14 or 16? at 15.2 and above, the uninstallation of any application does not work because the phone reboots

Wysłane z mojego EDI-AL10 przy użyciu Tapatalka
[Magisk] MohRez:
[MENTION=4470081]topjohnwu[/MENTION]

hi

supersu has an option to hide supersu icon from app drawer , how can I do this for Magisk ?!
[Magisk] Granite1:
I'm having the same exact behavior on my HTC 10 on Sprint. Never had any issues on Nougat, now I'm on Oreo, it's acting up.

Not even sure when it disappears, so I have no idea when to start a log.....:confused:
[Magisk] Guivre:
It won't let me post links because I don't have enough posts yet.

Can anyone help with my problem?
[Magisk] Didgeridoohan:
[MENTION=6329946]marius.podiuc[/MENTION], [MENTION=3393187]Granite1[/MENTION]

Isn't it enough to reboot for Magisk functionality to return?

A few questions:

How has your Manager been installed? Is it a normal user app? Installed as a system app? Included in the ROM? On sdcard?

Do you have any aggressive battery optimisation enabled, and if you do have you whitelisted the Magisk Manager?

ADB logcat when uninstalling an app.

ADB logcat when the Manager fails to open.

Use a launcher that can hide apps from the app drawer. Nova is one, but I'm sure there are others.
[Magisk] fil3s:
Hi. I haven't been following this thread so sorry if the question has already been answered. My usu unlocked H815T is failing to pass safetynet. I've tried a few different methods but nothing I have tried has worked. I'm on mokee 7.1.2
[Magisk] marcjero:
Hi,

I currently use a leeco LEX722 phone with Lineage 15.1.

I don't have root or anything special, just added the gapps. Bootloader is unlocked of course.

Problem is the SafetyNet CTS profile test is failing. As result the device is not certified in the Playstore.

Can Magisk help passing the SafetyNet test in my case ? I tried installing Magisk 16 with Magick Hide but the test is failing too.

I think that Magisk can hide some mods (root) but I'm not sure it can help the Lineage roms to pass this test ?

Thanks.
[Magisk] metrize:
After enabling magisk hide will android pay work if safety net passes or do I need to do
[Magisk] Didgeridoohan:
If you don't pass both tests that module will likely not help. Check here for troubleshooting tips:

https://www.didgeridoohan.com/magisk

Try the MagiskHide Props Config module.

Ok, a segmentation fault...

If you want to share more of the log, you can run "logcat -c" before grabbing the logcat. This way you clear the log before doing what you want to record and you won't end up with a lot of excess and useless information.
[Magisk] Guivre:
I uploaded my whole logcat file here, separated by error level thanks to the tool in that post you linked me: drive.google.com/open?id=1qLEZMF14SDYVCD1aoxAWw5L4VHMrv3mu
[Magisk] bobcov:
How exactly do you use Magisk? I have googled, I have gone through threads showing how to install it and set it up, but I am amazed that the very simple explanation of what comes next seems to be missing. I have several modules installed, but now what? Those modules don't appear anywhere else on the phone, there seems to be nothing to launch. Where do I even find explanations of what various options do? Why would I want to use Magisk Hide, for example? After installing debloater terminal emulator, how do I access it? There's no icon for it. What happens after Nano for Android NDK is installed? Nothing, as far as I can tell.
[Magisk] Didgeridoohan:
You can find lots of info on what Magisk is, here:

https://github.com/topjohnwu/Magisk/blob/master/docs/README.MD

And here:

https://www.didgeridoohan.com/magisk

For modules you'll find info in it's readme (which you'll find by pressing the module name/description in the downloads part of the Manager) or in its support thread (a link can usually be found in the readme). Many modules don't have any app or require any setup after installing. But, check the module documentation for usage instructions...

MagiskHide is used to hide root, custom ROM props, an unlocked bootloader and other stuff from apps and services that don't work on rooted devices or with custom ROMs, etc. Read more about it in the links above...
[Magisk] marcjero:
I tried this, it doesn't work.
[Magisk] facet_:
Thank you [MENTION=4667597]Didgeridoohan[/MENTION] for your interest, below the necessary log

https://www.dropbox.com/s/qtli6t5io1xb4mx/logcat.txt?dl=0
[Magisk] Didgeridoohan:
And it's only the ctsProfile test that fails, while basic integrity passes?

You've got more info on how to possibly fix it here:

https://www.didgeridoohan.com/magisk

Lots of errors in there... I should have asked last time, but what app is it you're trying to uninstall in this log?
[Magisk] marcjero:
Correct basic integrity is ok. I found something really strange : Android API is reporting a fingerprint that doesn't match the ro.build.fingerprint property (Lineage /.system/build.prop). The reported fingerprint is the device vendor fingerprint (factory rom). How is that possible ????
[Magisk] facet_:
Each application restarts the phone, in this case the McDonald's application. there is no problem with the v14, everything works, but the bank application, which runs on every higher version, does not work.

Help, please, because in order to uninstall something and use the bank application I have to change the version of magisk.

If necessary, I can restore the factory settings and try the application without any problems. Although I tried it and the effect is identical even with one bank application installed. The v14 does not have a bank but can be installed and uninstalled. Updating to v16 makes the bank operational but it cannot be uninstalled.
[Magisk] jenslody:
I had the same with my nougat rom, it reported the official fingerprint of my J5 (with or without magisk).

But it passed safetynet without issues, my current rom does not (cts false).
[Magisk] marcjero:
Thanks so I'm not becoming crazy :cyclops:
[Magisk] Granite1:
Unfortunately I have to reboot a couple times a day due to LTE issues I'm having. Keep losing LTE and only thing that brings it back is a reboot. So rebooting doesn't bring the functionality back. Magisk manager says it's not installed and I lose root privelages for my root apps.

Magisk was included with Leedroids ROM originally. Although when I lost it, I downloaded the .zip and I flash from recovery. I've flashed it from both an SD card and from internal memory.

It wasn't a system app originally I believe, I just used Titanium backup to convert to a system app. We'll see if that makes any difference.

I don't use any optimization apps, so I don't think that can be the issue.
[Magisk] bobcov:
Thank you VERY much. That was extremely helpful information. I got a few of the modules doing what they were designed to do and I will read the documentation now to see if I can deduce what is missing from the instructions regarding nanodroid. Thanks again.
[Magisk] jenslody:
MagiskManager should not be installed as system-app. This breaks at least the "hide-the-manager"-feature for no benefit.

It might have other side-effects. I don't think it's causing your issues, but who knows.
[Magisk] guest4711:
Do you really loose root when rebooting? I know that soft/fast rebooting does not re-intialize everything, so Magisk is not working for me in this case. But after turning off power and then switching the device on again everything is fine (for me).
[Magisk] gewe:
Hello,

I am trying to install an OTA update (March 2018 security patches). Last time I uninstalled Magisk, restored the original recovery, flashed the complete ROM, and then reinstalled TWRP and Magisk.

This time I can not find a complete ROM, so I tried the following:

boot into TWRP;

run the Magisk uninstaller (the latest, 20180328);

flash stock recovery;

flash stock boot;*

reboot;

start OTA install.

The update fails. Progress bar goes to about 25% and then it says "Error". There is no information why the update failed.

* I first tried without flashing boot, because the Magisk uninstaller already restored it. But the update failed.

Where can I find the reason the update failed to install? Are there any logs?

Am I missing something in the steps I took?

Device information: Moto G5S Plus, Android 7.1.1 (January 2018 security patches), TWRP 3.2.1-r16, Magisk v16.0, Magisk Manager 5.6.4 (112).
[Magisk] demonoidmaster:
Delete the ota zip and redownload or download the full rom update zip
[Magisk] teddy0209:
Your system is probably altered... You should keep a system.img backup after every successful ota...
[Magisk] gewe:
I redownloaded the OTA every time. Unfortunately, as I mentioned, I can not find a full ROM with this update.

I do have a full ROM of the previous update. Since I have no idea what has changed system, what would/could I lose when I flash the system.img_sparsechunk.* files?