yashsingh1/xdaforums huggingface dataset:
[Magisk] prathamb:
Thanks will try later but unfortunately I don't have log of magisk installation.

Should I upload boot.img so that someone can view it and check it ?

Patched boot.img : with stock boot.img carrying out any modifications form twrp will cause a bootloop ( eg installing system SuperSU with stock boot.img ) so I had flashed patched boot.img which will prevent bootloop while installing , backup, restore

Edit 1 : I don't know coding/developing hence can't patch boot.img manually

Edit 2 : here is my boot.img if anyone can check it will it work with magisk or not (I have zipped it so that I can upload it , please unzip it to check boot.img)
[Magisk] ksio89:
I tried, doesn't work :( Only uninstalling Xposed Installer Magisk version works.
[Magisk] Oberbergler:
Hi :)

i have a car head unit with Android 8. The unit has no fastboot option, it uses instead an SD card which automatically flashes the system files when inserted while booting. To root the unit I have created a modified boot.img with Magisc but I don`t know how to flash it. Can I simply insert the modified boot.img in the flashable zip instead of the original one?
[Magisk] jcmm11:
That's what I would try. As long as the auto flash doesn't verify the images via signatures/md5 etc. it should work (based on what you've said). The only way to know for sure is to try it and see what happens.

Just make sure you can recover if it doesn't work.
[Magisk] prathamb:
Just asking if I install boot.img patched by magisk and if something goes wrong , will I be able to restore it by reflashing original boot.img or by restore boot partition of nandroid backup ?
[Magisk] gothicVI:
Yes. Either should work.

Gesendet von meinem Moto G (5) Plus mit Tapatalk
[Magisk] prathamb:
Error log

I tried flashing patched boot.img but it gave error , then tried zip which created bootloop ( flashed stock boot.img to boot ) , here is complete log of process , hope it will help to develop magisk

Edit : some people were able to flash magisk on their device (k3 note ) but maybe older version of the one having phhs superuser
[Magisk] sbreit:
Hi everyone!

I've installed Magisk 16.4 on a Pixel 2 "Walleye" using twrp (just booted, not installed). When I launch Magisk Manager right after booting everything works. When I start Magisk Manager a second time, it asks me about installing Magisk and reports Magisk is not installed. However, root is working as expected.

This is the log, in case that helps:

05-24 09:29:37.819 687 687 I Magisk : ** Initializing Magisk
05-24 09:29:37.911 687 687 I Magisk : * Creating /sbin overlay
05-24 09:29:37.912 687 687 I Magisk : * Mounting mirrors
05-24 09:29:37.912 687 687 I Magisk : bind_mount: /sbin/.core/mirror/system <- /system_root/system
05-24 09:29:37.912 687 687 I Magisk : mount: /sbin/.core/mirror/vendor <- /dev/block/dm-0
05-24 09:29:37.915 687 687 I Magisk : bind_mount: /sbin/.core/mirror/bin <- /data/adb/magisk
05-24 09:29:37.915 687 687 I Magisk : * Setting up internal busybox
05-24 09:29:38.480 862 862 I Magisk : Magisk v16.4(1642) daemon started
05-24 09:29:38.482 862 948 I Magisk : * Starting MagiskHide
05-24 09:29:38.482 862 948 I Magisk : hide_utils: Hiding sensitive props
05-24 09:29:38.483 862 948 E Magisk : fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
05-24 09:29:38.483 862 948 I Magisk : hide_list add: [com.google.android.gms.unstable]
05-24 09:29:38.484 862 950 I Magisk : ** late_start service mode running
05-24 09:29:38.518 862 948 E Magisk : fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
05-24 09:29:38.518 862 948 I Magisk : proc_monitor: init ns=mnt:[4026531840]
05-24 09:29:39.217 862 948 I Magisk : proc_monitor: zygote ns=mnt:[4026533854] zygote64 ns=mnt:[4026533855]
05-24 09:29:53.187 862 948 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=4800 ns=mnt:[4026534060])
05-24 09:30:16.020 862 948 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=6706 ns=mnt:[4026534037])

Cheers
[Magisk] Brodelpiet:
If I fail the certification for my device in the Play Store in the past but are now able to pass safety net. Is there a way to enable the play store to re-check the certification? So I can download apps like Netflix?
[Magisk] :
Wipe Play Store's cache and data.
[Magisk] _RM_:
Hello everyone, first of all congratulations for this project ;)

I've been asking for help, I recently tried lineage v15.1 and I also installed magisk v16.0.

When I try to enter the magisk it opens but closes soon what it might be?
[Magisk] xt1622-blue27:
Magisk on Moto G4 (XT1622)

Hi,

I'm trying to install Magisk on a Moto G4 (XT1622) running Android 7.

i did format the data-filesystem to ext4 (it was f2fs) according to the troubleshoot "Some Motorolla devices' stock kernel ships with a flawed F2FS implementation. Change to a custom kernel with the fix or format data to ext4.".

however i still get a black screen when booting.

is there anything else to do?

i want to use the stock kernel and not a custom one if it is at all possible.

kind regards,

xt1622-blue27
[Magisk] DB126:
I have similar passions on Moto devices (stock kernel, ROM) and found the F2FS Loopback Bug Workaround module works a treat on G4/E4/X4 (presumably Zxx) devices. You may need to flash a no verity opt encrypt script as well. Consult your device forum for details.
[Magisk] g104:
I'd like to disable for limited storage.
[Magisk] xt1622-blue27:
thanks for the hint! i had a look at it. as far as i understood this works when the data filesystem still is f2fs.

i formatted mine to ext4 however. isn't there a way to get magisk to work with the ext4 filesystem?

if not i will try your workaround...
[Magisk] Didgeridoohan:
Have you made sure that your device can boot at all with an ext4 file system? Some f2fs devices can't...
[Magisk] xt1622-blue27:
yes. boots without any problems...
[Magisk] DB126:
Not a fan of reformatting data partition. Works for many/most but presents another deviation from 'stock' that must be managed.
[Magisk] devil-kin:
I've recently started using LOS 15.1 on my OP3. Magisk works... until I enable the repackaging so the Magisk Manager is also hidden. At that point, su requests fail, magisk manager fails to open, everything just hangs. Removing the repackaged version and returning to the "stock" manager makes everything work again.

Is this an issue? Is there something to try?
[Magisk] Didgeridoohan:
Logcat?
[Magisk] fiverings:
I updated my pixel XL to Android p preview 2

Now I can't get magisk to work right.

The magisk manager is 5.7.0 and I'm on v16.4

On the manager, the upper one says "invalid update channel. First in did a uninstall magisk, then installed v16.4 and rebooted I to phone.

The magisk manager did not install like it normally would due. Then I installed it manually. Any one have a fix?
[Magisk] fiverings:
Ok, it's working now. I just left it alone for about 4 hours and for some unknown reason, it fixed it self. All good now
[Magisk] 135Shadowsoul:
Hallo every1,

since a few weeks i am facing an issue with magisk (i dont know if its a magisk problem or something else), let me descripe what happens:

During boot (and a short time after), everything with logging (adb logcat) is fine, but after some time (depending on buffer size; higher buffer size => later) i get a "read: unexpected EoF!". If i "logcat" as root later with adb or terminal app, i get "logcat read failure". If i "start logd" as root after logcat starts failing, logcat is running again, but it seems magisk does not see it, because if i (always as root ofc) "magiskhide --disable" and "magiskhide --enable", magisk tells me, logcat is disabled. But with logcat apps like CatLog or adb/terminal i can get loggs.

And because magisk does not detect logcat anymore after restarting, magisk hide looses functionality. I am not able to pass SN or use apps with root detection. The attached .zip contains different logs: magisk log, magisk install log and logcat during boot with different buffer sizes. I also tryed clean reinstall of magisk, but it did not help.

note: since this problem appears, i looks like my phone has a extreme battery drain and gets (even in "idle") quite warm...

I hope some1 can help me...

Device Info: Samsung Galaxy S4 (GT-I9505) with LOS14.1 (link see signature) and Magisk v16.4
[Magisk] Artim_96:
Well, have you tried older Magisk versions or different ROMs?
[Magisk] 135Shadowsoul:
Magisk v16.0: same problem

Different rom: not yet.

But i did no change on the ROM arround the time, the problem appered. i have also asked in rom thread, but no answer => seems to be not a rom only problem
[Magisk] 10thDmenxn:
I recently flashed the Sac23 Oreo S9 port rom on my S7E, and all was working very well. However, Magisk said there was a download, so I downloaded/installed it. Since this time, Magisk is NOT passing safety net. I have searched around, but haven't found anything on this. So wondering if anyone here has any solutions or suggestions. Thanks.
[Magisk] roboprint:
Guys,

In attachment two polish bank apps. The older one works without any issue.

Unfortunately the last update from 16-05-2018 wont works. Looks like app see root despite the hide option in Magisk is ticked.

I try to use Magisk 16.0 and 16.3 nothing helps. Can someone check what is wrong end help polish community? Maybe small Magisk update. I am on HTC U 11 with last Leedroid rom.
[Magisk] Didgeridoohan:
Toggled MagiskHide off and on in the Manager settings?

More: https://www.didgeridoohan.com/magisk/MagiskHide#hn_MagiskHide_Issues

https://www.didgeridoohan.com/magisk/MagiskHide/#hn_Hiding_root_from_apps
[Magisk] SimplyCity:
Have you tried the trick with Google Play Services? If not do this and check again and report if it works (ps. Confirmed working on Santander Bank app) :

1. Your device has to pass SN. If passed, go to next step, if not, well search for how to.

2. Turn on Magisk hide for that app and run the usual setup (just for testing).

3. If it fails then wipe out data for that app and force close it.

4. Go to device settings > apps > Google play services (Usługi Google Play) > permission... and disable phone there (other words: turn off phone access permission for Google play services).

5. Now open the app and do usual setup.... it'll work now.

6. Enable phone permission if u want.

Few additions:

# the app may say it won't work properly without phone access... don't bother about it.

# won't work if safetynet isn't passed

# don't forget to hide root

# the trick shouldn't have impact on phone's behavior

;)

Wysłane z mojego SM-N950F przy użyciu Tapatalka
[Magisk] 10thDmenxn:
Hey, thanks for you reply. I tried to tick it off and back on several times and I'm still unable to pass safety net. Any other ideas?
[Magisk] jenslody:
Do you have a running logd and a non zero logbuffer size ?

Does MagiskHide work ?
[Magisk] Didgeridoohan:
Yes, and pretty much all of them can be found by following that link I posted for you...

https://www.didgeridoohan.com/magisk
[Magisk] 10thDmenxn:
Okay, so I am checking out your post. But I do not understand what you are saying at the end of your comment, about renaming and repackaging MM? Thanks!

---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------

MagiskHide is NOT working, and I'm not sure what you are talking about, "a running logd and a non zero logbuffer size"? Suddenly I feel like a noob again! lol.
[Magisk] Didgeridoohan:
That's a function of the Magisk Manager (in the Manager settings), where you can hide the Manager by giving it a random package name (repackage it). It doesn't have an impact on SafetyNet, but there are plenty of apps that look for the Manager package name and don't let you use them if they find it.
[Magisk] 10thDmenxn:
Lol. You've got to be the fastest response on all of XDA!!! :good: Okay, so yeah, I've looked at that, but have not renamed it, as I hadn't researched what the effects of doing so would cause. So if I rename it, Magisk will still work exactly as it does now, only under an assumed name?
[Magisk] Didgeridoohan:
Yes, but it has zero impact on your issue with MagiskHide.

MagiskHide troubleshooting tips:

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

And when asking for help, it's good to provide logs:

https://www.didgeridoohan.com/magisk/MagiskHideHelp
[Magisk] daddylonglegs:
Is there any way to get Magisk working with Xposed and GravityBox?

I've been using Magisk with Xposed for a while now, along with GravityBox. I usually have the issue where after I install Magisk my phone won't boot until I change the boot image size to the full amount available using the mm command in twrp. However, with the latest update for my Google Pixel 1, my phone will not start with Xposed being enabled. I am using the SDK 27 version of course. This is pretty disheartening because Gravitybox is 95% of the reason I root in the first place. Is there anything I should know about so I can boot my phone with Magisk, Xposed, and Gravitybox all being enabled?
[Magisk] 10thDmenxn:
It's all good, after I went to modules, navigated the path to my Magisk 16.0, and clicked it to downgrade from 16.4 back to 16.0, everything started working. Funny, I had gone back to 16.0 yesterday, and it still didn't work. But in the interim, I also upgraded from Sac23 S9 port, to the newer Sac23 Tester 5.5.2 rom. So I guess being on the newer rom also helped. But after downgrading, it passed safety net, and hide is working. So I just want to say thank you for all of your time and efforts.

I do have one off-topic question. Do you know where outdoor brightnes is hidden? For some reason I can't seem to find it now. Lol. So thanks for all your help. I do appreciate it. Cheers!
[Magisk] sbreit:
null pointer dereference on Pixel 2 "walleye"

Crashing with null pointer dereference on Pixel 2 "walleye"

Reboot always fixes it (for a few hours)

* Google Pixel 2 Walleye

* OPM2.171019.029.B1

* Android 8.1.0 Patch Level 5/5/2018

* Magisk 16.4 installed via booted (not flashed) TWRP

* No other customizations (Modules, Kernel etc.); stock apart from Magisk

Magisk somehow crashes some time after reboot, usually a few hours but less than 24. Only thing I notice is that Magisk Manager offers to download/install a "new" version.

Please see attached logs for details.
[Magisk] roboprint:
Unfortunately this is not working, also Magisk Manager Hide not working too :(
[Magisk] Didgeridoohan:
Have you tried everything in the link I gave you?

When does the app trigger? Since you need an account with the bank it's hard to test anything else except for opening the app. And that works fine...

If nothing else, grabbing a logcat when the app triggers might show something.
[Magisk] roboprint:
Yes, i tried all from the link. The issue is that app is installed but few function ( like login using finger and contactless payments) are blocked. Rest is working.

This is something coming from the update.
[Magisk] Didgeridoohan:
So grab that logcat when opening the app and trying to use the blocked features. That way there'll at least be something to work with.
[Magisk] lollazzo:
I flashed superSu and xposed.

Now I would like to use magisk.

What I have to do?
[Magisk] teddy0209:
Remove supersu... Restore your boot.img. flash magisk...
[Magisk] roboprint:
The blocked features are not visible. This looks like the application disable them during installation process.

So far its not possible to do because bank service for this app is temporary unavailable.
[Magisk] lollazzo:
Is it not necessary to remove xposed?
[Magisk] Didgeridoohan:
No, not if you want to keep using it. If you want to use Magisk to circumvent root detection (SafetyNet etc), it's a different story. Easiest solution in that case would be to uninstall your current Xposed and use a Magisk Xposed module. That can then easily be disabled whenever you need to use any app or service that doesn't work with Xposed installed.
[Magisk] RandomPooka:
Why are you wanting to use magisk now? If it's because of magisk hide and the ability to pass SafetyNet checks, that won't work until you ditch XPosed. So, if Xposed is important to your setup and superSu allows you to achieve your goals (other than hiding root0, there's no advantage to switching to magisk that I can think of. And switching to magisk won't allow you to hide root anyway if you're still using xposed, as far as I know.
[Magisk] lollazzo:
Last question.

I have the zip file of unrooted rom. How I can flash boot.img?

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

Supersu is not open source. I do not trust much of the owner company
[Magisk] Ja_som:
You can flash the zip file, you will have untouched system and also "stock" boot.
[Magisk] RandomPooka:
Fair enough. I just wanted to be sure you weren't expecting to be able to hide root and went through it all to find out that you can't.
[Magisk] Didgeridoohan:
[MENTION=7289357]Parzival_UY[/MENTION]

From your log it looks like you have Xposed installed. SafetyNet will always fail with Xposed active... And it doesn't matter that it's systemless, it can't be hidden.
[Magisk] xt1622-blue27:
Magisk on Moto G4 (XT1622)

hi flipmode_11,

device: Moto G4 (XT1622)

rom: stock (Android 7.0, security patch level april 2018, build number MPJ24.139-63)

kernel: stock (3.10.84-... dated march 28, 2018)

magisk: 16.4

magisk manager: 5.7.0

logs: I cannot provide logs since the smartphone does not boot at all. i just get a black screen

steps to reproduce: format data-partition from f2fs to ext4. install magisk with twrp.

with a custom kernel (e.g. elementalx) it work fine. the problem with the stock kernel

thus is not (only) the f2fs data partition.

kind regards,

xt1622-blue27
[Magisk] daddylonglegs:
Is there any way to get Magisk working with Xposed and GravityBox?

I've been using Magisk with Xposed for a while now, along with GravityBox. I usually have the issue where after I install Magisk my phone won't boot until I change the boot image size to the full amount available using the mm command in twrp. However, with the latest update for my Google Pixel 1, my phone will not start with Xposed being enabled. I am using the SDK 27 version of course. This is pretty disheartening because Gravitybox is 95% of the reason I root in the first place. Is there anything I should know about so I can boot my phone with Magisk, Xposed, and Gravitybox all being enabled?

Keep in mind that I do not care if safetynet fails. Thanks in advance!
[Magisk] KamilKiri:
I keep receiving this error in my logcat, what's that? When new version will be available? Thanks

Samsung Galaxy S9+ / Oreo 8.0
[Magisk] Parzival_UY:
That's it!! Kind of stupid of my part not to figure out this started happening after installing Xposed.

Sorry for the inconvenience.

Thanks a lot.
[Magisk] guest4711:
I do not agree. Magisk allows me to use modules for all my mods to the ROM I flash. So when I update the ROM I don't need to flash any mods (like microG), fonts or to change some configurations (like gps.conf, hosts e.g.). I flash magisk and all is working again...

So there is a big advantage over using LOS-su-addon, SuperSU or other root solutions... [MENTION=2089857]lollazzo[/MENTION]
[Magisk] Parzival_UY:
I'm looking for some help regarding Magisk Modules. I've already installed three modules, which I'm sure at least one of them should install an app (App Systemize Terminal; the other are DNSCrypt and Doze for Play Services). The problem is none of the apps are showing, I can't even see them on the Application list under Settings.

I don't know if it is related but I have preserve enforce encryption checked.

Thanks
[Magisk] Didgeridoohan:
None of those install apps...

For the Terminal Systemizer you'll need to use a terminal emulator to run the systemize command. Same thing with DNSCrypt and the Doze module, but neither of does have any commands you can run.

All of this is explained in the module documentation, which you should probably take a look at... Just click the module name and description in the Downloads section of the Manager and you'll find it.
[Magisk] Parzival_UY:
Ok, sorry. This was my bad. I saw a lot of posts which pointed that an app is installed, even saw a couple videos with that. I should just gone to the documentation, didn't know that's how you access it. Apologies.
[Magisk] Didgeridoohan:
No worries. There used to be another systemizer module that did include an app. It's been discontinued... Similar names, so it's easy to mix the two up.
[Magisk] topstarnec:
device codename: mido (xiaomi redmi note 4)

rom: official lineage 15.1 upgraded from 14.1

problems: magisk no root, magisk install/uninstall error 1, can not delete magisk.
[Magisk] Artim_96:
Error codes from TWRP don't really help, we need the installation logs which should be located in /cache (or in /tmp when you are still in TWRP after flashing)

And there is always a way to uninstall Magisk. In worst case just install the ROMs stock boot image and manually remove /data/magisk.img
[Magisk] flipmode_11:
If you cannot boot, you may have to restore your boot (and other partitions depending on device) to stock or your ROM's boot.img, then patch and flash. Have you tried extracting the boot.img from the stock or custom ROM ZIP? Do you have a TWRP backup on your device?

If this fails, this might be a question for [MENTION=4667597]Didgeridoohan[/MENTION] or TopJohnWu as I have not messed around converting partitions...

Good luck!
[Magisk] xt1622-blue27:
i installed the full stock firmware from scratch.

the notes & troubleshoots say that

i thus formatted data to ext4. but this does not seem to be the only problem since the g4 doesn't boot.

with a custom kernel (i tried elementalx) the g4 boots with either a f2fs- or an ext4-data-partition.
[Magisk] gothicVI:
Maybe the stock kernel/rom can't handle ext4 or a non f2fs data partition.

Anyhow if a custom kernel works go with that.

Gesendet von meinem Moto G (5) Plus mit Tapatalk
[Magisk] xt1622-blue27:
i tried that. the custom kernel works fine with either a f2fs- or an ext4-data-partition.

i'd rather stay with the stock kernel.
[Magisk] roboprint:
I just update the app. Logcat in attachment. I hope something will be visible
[Magisk] Didgeridoohan:
The f2fs issue doesn't cause bootloops, it just prevents the Magisk image to mount properly, leading to issues with installing modules. You've got a different thing going on.

You can try to experimenting with enabling and disabling dm-verity and forced encryption when installing. If that doesn't work you can try to flash a boot signer zip after installing Magisk.

And if nothing else works, go with the custom kernel. There are no drawbacks...

---------- Post added at 11:39 ---------- Previous post was at 11:29 ----------

I don't see anything apparent at a quick glance. Without actually testing the app myself, it's really hard to troubleshoot. For now, I think you're on your own...
[Magisk] firozpatel:
hi hope your okay

i have an issue with my s6 edge 6.0.1 not able to deep sleep, the issue was solved through chainfires supersu, i have kernals that help this matter but it seems to not want to work with magisk

is there anyway you can help me, my battery just dies so quick thank you
[Magisk] schlimmchen:
Hello everybody!

After upgrading LineageOS 15.1 to 20180528 on my cheeseburger (OnePlus 5), the device always boots into fastboot. When restoring the non-Magisk boot image in TWRP, everything is fine again. As soon as I install Magisk (v16.0 or v16.4), the phone only boots into fastboot mode.

It seems nobody else wrote about this so far?! Who has similar issues or know the cause of this?
[Magisk] xt1622-blue27:
does anyone with a g4 know how to switch off dm-verity?

i couldn't find anything...

VerifiedBootSigner.zip doesn't result in a working boot image.

i couldn't get BootSignature.jar to run on either linux or windows.

guess i'll just give up if nobody knows how to simply switch off dm-verity...