yashsingh1/xdaforums huggingface dataset:
[Magisk] spleenandcigars:
That sounds quite dangerous, as I've seen some hard brick complaints by messing with slots.

Thanks for that info. I'll wait patiently. Good to know that it wasn't something messed with my device.
[Magisk] dethknite:
It is actually extremely simply... use the deuce-flash-all-v4.5 script for Pixel devices... best way to get both a/b on the same version. https://xdaforums.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
[Magisk] monsterkruemel:
Hello. I am running magisk 16.7 (1671) on my Mi Mix 2 with lineage os 15.1 (2018-08-13). My banking app (banking4) does not work anymore, so i checked my safety net status on magisk. It says "the answer is invalid". Anyone with a clue for that?

Magisk log says:

"09-20 18:01:53.843 738 738 I Magisk : ** Initializing Magisk

09-20 18:01:53.883 738 738 I Magisk : * Creating /sbin overlay

09-20 18:01:53.888 738 738 I Magisk : * Mounting mirrors

09-20 18:01:53.889 738 738 I Magisk : mount: /sbin/.core/mirror/system

09-20 18:01:53.889 738 738 I Magisk : mount: /sbin/.core/mirror/vendor

09-20 18:01:53.890 738 738 I Magisk : bind_mount: /sbin/.core/mirror/bin

09-20 18:01:53.891 738 738 I Magisk : * Setting up internal busybox

09-20 18:01:53.969 745 745 I Magisk : Magisk v16.7(1671) logger started

09-20 18:01:53.979 741 741 I Magisk : Magisk v16.7(1671) daemon started

09-20 18:01:53.986 741 748 I Magisk : ** post-fs-data mode running

09-20 18:01:53.988 741 748 I Magisk : * Mounting /data/adb/magisk.img

09-20 18:01:54.038 741 748 I Magisk : * Running post-fs-data.d scripts

09-20 18:01:54.039 741 748 I Magisk : * Running module post-fs-data scripts

09-20 18:01:54.039 741 748 I Magisk : * Loading modules

08-20 15:54:37.981 741 938 I Magisk : ** late_start service mode running

08-20 15:54:38.088 741 938 I Magisk : * Running service.d scripts

08-20 15:54:38.089 741 938 I Magisk : * Running module service scripts

08-20 15:55:48.904 741 6811 I Magisk : * Starting MagiskHide

08-20 15:55:48.904 741 6811 I Magisk : hide_utils: Hiding sensitive props

08-20 15:55:48.905 741 6811 I Magisk : hide_list: [com.google.android.gms.unstable]

08-20 15:57:29.155 741 6811 I Magisk : proc_monitor: com.google.android.gms.unstable"
[Magisk] Paschfire:
Had you searched the thread before posting, you'd already know the answer to this question.

Wait for the next Magisk update.

https://mobile.twitter.com/topjohnwu/status/1029239685338419200
[Magisk] monsterkruemel:
I have read many pages of this thread, but I must admit I have not read all pages. :( I'm sorry.

Thanks for giving me a hint anyway.
[Magisk] apophis9283:
Using the search function would have made it so you didn't need to read all the pages. Please use the search function before posting here.
[Magisk] monsterkruemel:
I promise i will do so in the future. Thank you for your kindness an advice. :o
[Magisk] shiftr182:
Hi all, I have a Pixel 2 XL with stock PIE, rooted with Magisk 16.7(5)... (Nathan's Build) and TWRP 3.2.3.0. I have noticed that since Magisk 16.4, if I turn off the phone while charging it gets stuck on a screen with a big white charging battery on it. My issue is that the screen does not time out. There is no animation or anything. Prior to Magisk 16.4, it would show the battery with an animation like it was charging, then time out after 15 or 30 seconds and the screen would go black. Now I either have to leave my phone on, or I am stuck with a big white battery lit up on my screen. Anybody know a way around this?

The icon looks like the one on these screens.
[Magisk] Badger50:
About the only work around I've seen is to charge with the phone on. Mine does it too ?
[Magisk] whitewallman:
Magisk 16.6 charges as expected on my Pixel 2 XL with the same setup. Only 16.7 exhibited the charging issue for me.

Cannot produce log because issue happens only when powered off.
[Magisk] shiftr182:
It does work on 16.6! Thanks!
[Magisk] dethknite:
Another possibility is the A/B partitions are not on the same bootloader. I hit a few snags initially with this as I never OTA, only flashAll without the -w wipe. A great way to fix this is to use the deuce-flash-all-v4.5 script from here
[Magisk] Artim_96:
I don't think Motorola has any devices using the A/B petition scheme
[Magisk] sash11:
I put mine into Download folder. Magisk patched it without any issues. Flushed patched_boot.img through fastboot. Rooted now. What do you mean by Target image location? Why is it in /data?
[Magisk] Homeboy76:
[MENTION=5563377]spleenandcigars[/MENTION]

I think that tool/Script is for Pixel2/Pixel2 XL not the Pixel/Pixel XL.
[Magisk] JimmyLippitt216:
Recently switched up custom roms on my Note 3 and am unable to pass safety net. Tried on Stable release and beta release, when I tap on safety net it gives message saying Response is Invalid. Searched thread and removed all modules I was using them rebooted. Still can't pass safety net and get same message. I went to AOSP Rom from Samsung Port. Had no issues passing safety net there.
[Magisk] apophis9283:
Page 1042 . It's there. He even linked the developers Twitter post
[Magisk] DanGLES3:
Response is invalid is a bug on magisk manager,magisk was using an old api for checking safetynet and google recently deprecated this api and magisk didn't update to the new api,it doesn't mean you don't pass safetynet it just means magisk can't check safetynet status
[Magisk] gadingww:
Last week I installed Android Pie from Project Treble and also Magisk 16.7 too in my Xiaomi Mi 5s. After some of usage, the device crashed and rebooted to TWRP quite often. Then I came back to LOS 15.1, installed Magisk 16.0 but the problem still persisted. After uninstalled Magisk, device are no longer crashed and reboot. Any idea of what I've done wrong and how to fix it? Tried format data through TWRP but didn't help
[Magisk] yochananmarqos:
No idea without logs. Also they're required per the OP. See here for help: https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] Gygun:
Is there another way to hide root? (like something I could flash to make it work permanently?)

The hide option that comes with the manager doesn't work for me.

If I use another random app to hide it, it works, but it reset after every reboot, and sometimes I lose root and I need to reeboot again to make it work.

Thanks
[Magisk] Paschfire:
You provide no logs, no information regarding your device or its current setup...

Not sure what you expect anyone to suggest?
[Magisk] Gygun:
My bad :( It was a Xiaomi Mi Mix 2, with a custom chiron rom. I have the log now but...

I... just reinstalled the manager and now it works. I don't know what to say.

Sorry to wasting your time. I'm so embarrassed right now... Sorry.
[Magisk] Paschfire:
No ETAs are ever given, its also extremely rude to ask.

So simply learn to be patient and wait for it just like everyone else has too.
[Magisk] Didgeridoohan:
It was not deleted because of a link to Reddit... It was deleted because it's off topic for the Magisk beta development thread! Simple as that...

You are impatient, and have already been told so by a few people. But, since you are, I suggest you simply install one of the unofficial snapshots that are provided by a few users here in the Magisk forum. That way you'll have the latest code all the time and don't have to wonder when the next official release will be... :good:

I think I remember [MENTION=4470081]topjohnwu[/MENTION] adding something to the code that would fix the "Bad system call". You could try an unofficial snapshot if you don't want to wait for an official release.
[Magisk] apophis9283:
If your post got deleted, its for one of these reasons

off-topic, irrelevant, not the proper thread (see previous reason), did not follow through with the request of logs when reporting an issue , or failing to use the search function.

I remind everyone to please take the time, read the OP and do what is required to post, and to please post in appropriate threads.
[Magisk] H0wdy:
I hope so. I'm having the same issues with G screen after installing.
[Magisk] Wesley_NL:
ok a logcat from adb logcat

my device , samsung galaxy s9+ sm-g965f G965FXXU2BRG6

stock rom and kernel only root aplied from dr ketan

its just safetynet

hope i done it right
[Magisk] SacredDeviL666:
Usual cleanup done followed by few posts has been moved to Magisk General :highfive:

Thank you all for your participation :cool:
[Magisk] Tecalote:
New issue on Huawei Phones with OTA Patch: Patch01

[MENTION=4470081]topjohnwu[/MENTION]
[MENTION=4667597]Didgeridoohan[/MENTION]

New issue on Huawei Phones - Mate 10, Mate 10 Pro, P9 - Huawei roll out a new OTA called: "patch01". In the changelog is some fix mentioned (example: mms...) but the main patch is to disable the possibility of Root.

That means: if someone flash Magisk with TWRP, or flash patched_boot.img to ramdisk and reboot the phone, Phone get stuck on the splash screen: "Your device cannot be trusted..." :)

Only flashing back the original Huawei ramdisk.img helps to boot again to system. But no Root with Magisk is anymore possible.

Downgrade helps (if available, because for some Phones like Mate 10 it is dangerous to downgrade, if the Downgrade Firmware has another Xloader.img... but this is another story)

→ So, for Users of Huawei Phones it is better not to install OTA with Patch01 and disable Systemupdate in /system/app/HwOUC - rename HwOUC.apk to HwOUC.bak

I attach here the patch from Huawei for P9 - may you take a look, thanks :)
[Magisk] Didgeridoohan:
And this is regardless of dm-verity being disabled?
[Magisk] georgekav33:
Magisk on the NXP MX8 AOSP Platform

Hello I am trying to install the Magisk using the patched img approach (no twrp recovery available) on a AOSP Android 8.1 on a development device of NXP MX8M, soon to be the main certified device by Google for Android Things 1.0. This is A/B and treble scheme arm64 device. SELinux was enforcing, and dm-verity enabled.

Concerning Magisk, the stock boot.img is patched successfully (see log attached) but after installing in with fastboot in boot partition, the Magisk is not actually there: files of Magisk in /sbin/ are missing and of course Magisk manager reported it as uninstalled. Tried both with keepverity true and false.

Could it be that the patcher got the wrong partitions as in this device we have much less that the locked down mobiles phones?

Can we enable a more verbose log?

Here is the list of partitions:

lrwxrwxrwx 1 root root 20 2000-01-01 00:00 boot_a -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2000-01-01 00:00 boot_b -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 47 2000-01-01 00:00 bootloader -> /dev/block/platform/30b40000.usdhc/mmcblk0boot0
lrwxrwxrwx 1 root root 21 2000-01-01 00:00 fbmisc -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2000-01-01 00:00 metadata -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2000-01-01 00:00 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2000-01-01 00:00 presistdata -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2000-01-01 00:00 system_a -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2000-01-01 00:00 system_b -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 2000-01-01 00:00 userdata -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2000-01-01 00:00 vbmeta_a -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2000-01-01 00:00 vbmeta_b -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 2000-01-01 00:00 vendor_a -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2000-01-01 00:00 vendor_b -> /dev/block/mmcblk0p9

Finally, since we are building the AOSP from sources, is there any guide for modifying directly the ramdisk/boot sources?
[Magisk] Didgeridoohan:
Is there any kind of information in the Magisk log?
[Magisk] georgekav33:
The /cache is unfortunately empty, it is like the Magisk daemon is never run.

I am attaching also the logcat of the patching procedure using the app.

I also tried to patch the boot.img with a different device, and the results are the same.
[Magisk] Didgeridoohan:
The boot image seems to be patched correctly, but like you say, it doesn't seem like Magisk runs at all. Are you sure you're flashing the patched image to the correct slot?
[Magisk] georgekav33:
Indeed that was the first I though.

However looking at the kernel (I have full console log)

Kernel command line: console=ttymxc0,115200 earlycon=imxuart,0x30860000,115200 init=/init androidboot.console=ttymxc0 consoleblank=0 androidboot.hardware=freescale cma=1536M firmware_class.path=/vendor/firmware androidboot.soc_type=imx8mq androidboot.storage_type=emmc androidboot.boottime=1BLL:0,1BLE:3898,KL:0,KD:0,AVB:2022,ODT:0,SW:0 androidboot.verifiedbootstate=orange androidboot.slot_suffix=_a dm="1 vroot none ro 1,0 3095928 verity 1 PARTUUID=66b27d57-a91a-4aec-a051-6ad4c0faea45 PARTUUID=66b27d57-a91a-4aec-a051-6ad4c0faea45 4096 4096 386991 386991 sha1 f7c35576e076f77d1224fd20d99e900954645fa8 0ce0b4ede22e3f24178f835743ba80875d089208 10 restart_on_corruption ignore_zero_blocks use_fec_from_device PARTUUID=66b27d57-a91a-4aec-a051-6ad4c0faea45 fec_roots 2 fec_blocks 390040 fec_start 390040" root=/dev/dm-0 androidboot.vbmeta.device=PARTUUID=b43e0c02-3ac4-4814-ba40-822e5e61e2e0 androidboot.vbmeta.avb_version=1.0 androidboot.vbmeta.device_state=unlocked androidboot.vbmeta.hash_alg=sha256 androidboot.vbmeta.size=3008 androidboot.vbmeta.digest=39b9ac7f694e5e548a534e59ebf0309a2994500b07f403fd9cf6b8d9d9d04c10 androidboot.vbmeta.invalidate_on_error=yes androidboot.veritymode=enforcing skip_initramfs
kernel @ 80080000 (25747968)
ramdisk @ 84000000 ([B]7083766[/B])
fdt @ 83000000 (44729)

it nearly agrees with the output size of magisk (the stock is 6838730)

KERNEL [25747968]
RAMDISK [[B]7083760[/B]]
SECOND [44729]
EXTRA [0]
PAGESIZE [2048]
NAME []

Can it be that the init rc scripts are not configured the same way as expected by Magisk and thus its init method is never run? Is there a guide for porting Magisk? Maybe I can try manually.
[Magisk] Wesley_NL:
Do this log helps to find out safetynet ?

Root sofar works fine but hide pokemon go wont work
[Magisk] Didgeridoohan:
I have absolutely no clue... :D I'm gonna link this to some people that actually know what they're talking about. Let's hope they have some idea...

That has absolutely nothing to do with Magisk beta discussion... Please keep Pokemon queries in the dedicated Pokemon Go thread: https://xdaforums.com/apps/magisk/discussion-pokemon-magisk-discussion-t3465722
[Magisk] georgekav33:
I think I am starting to have a clue. The device is a true A/B device, and as such, we have skip_initramfs argument which basically ignores the Ramdisk of the boot.img. So basically what we did with the patch of the boot.img by the app is to patch the recovery (the ramdisk belongs to recovery now).
[Magisk] Wesley_NL:
Yes ok but what about safetynet itself ? That belongs here right ?
[Magisk] Didgeridoohan:
Is that any different from the Pixel family? Because they can install Magisk just fine.

From the OP, regarding SafetyNet:

So... No. Keep it in the Pokemon thread or the general support thread.
[Magisk] otyg:
/dev/block/boot detection is broken in latest magisk manager (trying to upgrade to Magisk 16.7).

would it be possible to manually specify the location in the next Magisk Manager update?
[Magisk] georgekav33:
Indeed it should be close because also the MX8 has the latest features/recommendations of Google. BUT, I think it is different when we flash via zip. The binary of Magisk has access to all partitions, and thus by detecting the skik_initramfs, it mounts and modifies the system. When we give the boot.img to the App, it is possible that the script does not do the sanity checks of skip_initramfs, as it does with the recovery mode ; and even if it did, it has zero ability to modify the /system and the true ramdisk in there.

Next test to do is to do an old school root and then use the direct mode of the app. If the Pixel/Pixel 2 is not hard-code as device strings that will use the new skip_initramfs procedure then it should work.
[Magisk] H0wdy:
That's why Verizon Pixel XL gets stuck on reboot/G logo after installing magisk?
[Magisk] Homeboy76:
Not a question.

Maybe, you should try an Unofficial Magisk Build, you've tried just about everything else.

Go to Magisk General Support / Discussion by topjohnwu and read [MENTION=8126387]martyfender[/MENTION] post.
[Magisk] SacredDeviL666:
Thread Cleaned.

Removed Safetynet posts

Posts without logs

Posts about playstore certifications

Discussion related to other apps

Responses given to all the above & any other non-beta related post. (use the Magisk General Thread :- https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382

DO NOT POST LINKS for unofficial builds in an Official Beta Thread.

If i have removed any of your posts in error PM me so i can take a look and action accordingly.

Read OP before you start posting in this thread specially :- https://xdaforums.com/showpost.php?p=72588015&postcount=1

Thanks

SacredDeviL666

Forum Moderator.
[Magisk] Homeboy76:
Didn't know it was official :(, thought it was BETA.

The link was to Magisk General Support / Discussion by topjohnwu.
[Magisk] H0wdy:
Any ideas as to which one?
[Magisk] Homeboy76:
PM me don't want to go OT.
[Magisk] Ubimo:
What does this mean in changelog?

Add hexpatch to remove Samsung defex in kernel
[Magisk] Pretoriano80:
Hmm, while it's true that latest Huawei behavior goes against modding, we shouldn't expect that Magisk will always work. OEMs will always do their best to avoid rooting (for them it will always be a security isdue) and sometimes might happen that Magisk will be affected by a patch that it's not even direct attack to it. It was like that with other Root solutions even before Magisk.

Now back to this patch 01 issue, any of you tried to debug it while it gets stuck on booting? Did you guys tried to backup patch01's ramdisk and check it against previous stock ramdisk.

What about rolling back the previous kernel.img instead of rolling back to the stock ramdisk?

What i'm trying to say (while i'm not defending Huawei at all) is that so far we are just speculating, without proper logs or anything that could help us understand what changed and how could be fixed.

P.S. If i would be at Huawei HQ and my intentions would be all against rooting, then i would force a bootloader lock with an update. Adios rooting! ? (i really hope they won't go this far)
[Magisk] Tecalote:
Hi Mate,

We are currently trying to find out if it was an unintended side effect.

For this we will roll up the whole situation with the patch again on two phones and try everything what's possible to sort it out.

I think we will know it at the end of this week.

I will report the results with Logs.

There are also two new Firmwares, which aren't officially released, but available.

We will test them too and see if Root is still possible or not..
[Magisk] PrettyPistol555:
:rolleyes: I didn't see that this supports the OG Pixel XL (Marlin)

It specifically says "

This script is for the UNLOCKED BOOTLOADER pixel2 / pixel2 XL

"

If it does support original Pixel devices it might come in very handy.... :cool:
[Magisk] yochananmarqos:
It does not, but it's very easy to modify.

This is way off topic, FYI.
[Magisk] demonoidmaster:
he can just hold down vol - on boot to start up in safe mode

Or he could just delete his magisk img from data/adb and reflash the modules that work all over again or.. Do what guest4711 said about manually creating a file telling magisk to be disabled on boot

What you said about previous back or factory reset and clean flash is dumb, fixing an issue with a magisk module is simple, there's no need for such drastic measures
[Magisk] IzaacJ:
Samsung Galaxy S7 Edge (Exynos) with Stock Oreo and Magisk 16.7 regularly looses root and says Magisk ain't installed.

Don't find the logs atm (no logs available in MM and on the go) but will attach them later tonight.

However, this happens without any modules installed, usually my only module is V4A but tried now for a week with no modules and still regularly says Magisk isn't installed until a reboot, and then it works for a few hours or so.

Any ideas?
[Magisk] Didgeridoohan:
That means that both magiskd and magisklogd are killed off somehow. Otherwise one would respawn the other. If you can pull the Magisk log from /cache after it happens it might show something, but a logcat as it happens would likely be the best...
[Magisk] IzaacJ:
When this started to happen I tried to see anything in the log inside MM, but since I had to restart to get Magisk to work (and to access the log in MM) it was cleared and only showed since reboot.

Can't access /cache when the root+Magisk ain't working, and after reboot the Magisk log seems to be cleared. The backed up one is only showing init messages and hide_list and proc_monitor messages.

Is there some way to get access to /cache w/o reboot or is it automatically backed up at reboot? If so, there doesn't seem to be any errors.
[Magisk] Didgeridoohan:
The Magisk log is cleared on a reboot, but the previous log is saved as magisk.log.bak.
[Magisk] Jenanga:
That's not the topic of this thread
[Magisk] demonoidmaster:
Gmail opens for me, no issue here

Oh and you didn't read the OP, the manager (5.0.1) and v13 are used together, cannot use the manager with v12 and you cannot use v13 with 4.3.3 Magisk Manager

If you flash v12 you need to use Magisk Manager 4.3.3

---------- Post added at 08:04 AM ---------- Previous post was at 08:01 AM ----------

Because Xposed isn't simply an application...
[Magisk] demonoidmaster:
Tbh seems like a good idea since atm Magisk isn't on the playstore so that means Topjohnwu can just use the bundled apk in the zip that would then get modified with a varying name (example Magisk Manager-7654645 , numbers vary from user to user or whenever it is flashed) and an always changing signature that would change whenever you'd flash Magisk v13

Tbh i like the idea of having something be abke to take a standard apk (that has the same build and sig for everyone) and have some kind of mechanism then either mod the apk (refer to what i said above with the numbers) and install it.. No matter if Magisk is installed in /data/app or not (i went from v12 to v13 so mine is a user app, idk if v13's apk gets placed in /system/app or priv-app when zip is flashed with no Magisk app previously installed from playstore)
[Magisk] TheDevFreak:
Using a OnePlusX latest Resurrection Remix, using the magisk v12 release in core mode I pass safety net
[Magisk] slimdick:
On MI4C works ;)
[Magisk] LuciferIII:
I am interesed in the Safteynet bypass and i know its current situation, but i don't know if it will work on a custom ROM.

Will this work on lineage? (i know the instalation works, i am asking about the bypass)
[Magisk] Ja_som:
It does not work at this moment, we are waiting for new beta version, but yes, it was OK on my N7 II with LOS before Google patched it.
[Magisk] LuciferIII:
As said i know its current situation, anyway thank you!
[Magisk] Shished:
My phone passes SafetyNet.

I'm using latest beta build and have SafetyNet pass module for my phone and sdcardfs module enabled.
[Magisk] jpandino:
My Oneplus One passed safety net on the beta version of magisk but had to disable viper audio module.
[Magisk] vickybonick:
Hi topjohnwu, I'm the dev of Apps2SD, I see you implemented namespace separation in Magisk. My question is is there a way to connect to the global namespace similar to what i do in SuperSU using su -mm. Also can you please explain the difference between POST_FS, POST_FS_DATA and service.
[Magisk] teddy0209:
Might this be what you're looking for?, though I think he'll update it soon for the v13 release... https://xdaforums.com/showthread.php?t=3473486
[Magisk] white7561:
Yeah. The foldermount is not mounting properly. So I changed it to global namespace.. also it appears that u add "app2sd" binary at magisk POST-FS-DATA.d folder. I can confirm that it makes boot slower . It slowed down on the bootloader stage. Like when it says "Samsung Galaxy S8+"
[Magisk] gothicVI:
So is root...

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Magisk] vickybonick:
Thanks, that answers my second question

---------- Post added at 06:42 AM ---------- Previous post was at 06:41 AM ----------

Thanks for the report. I'll look into it