yashsingh1/xdaforums huggingface dataset:
[Magisk] :
Any news on the safetynet fail thats fixed with unchecking and rechecking magiskhide, that seems to be affecting mostly samsung users?
[Magisk] UselessShane:
Hey can any one help me.....I am installing a module NFS INJECTOR.But it is not getting installed.....but it is there in the installed module section

Here is the log:
[Magisk] Jannomag:
Like a crispy door stopper
[Magisk] jcmm11:
Post in the module thread https://xdaforums.com/apps/magisk/module-nfs-injectorv1-t3857231
[Magisk] MDV106:
Is there a way to make Magisk Manager load the downloads tag list quicker ? Everytime I open the app it loads forever until i force close it and open it up again. Only then will the download list load successfully. Any help with this ?
[Magisk] Digitarier:
no sd card access since update

as the title says: i have no sd card access since update to magisk v19...does anyone else got this problem?

it only occours when android booted up. in twrp i can access it and even install from it like before ¯\_(ツ)_/¯
[Magisk] kotuamoalt:
Have you tried one of the mods that allows SD card access?

---------- Post added at 03:06 AM ---------- Previous post was at 02:57 AM ----------

My point was, we can't guess which module you're referring to either, without you listing any modules.

"I was just being lazy". I agree.
[Magisk] jasonbiggs:
Yah. I posted elsewhere that mine began to work after clicking on email link from Google pay asking me to finish setting up my cards. Wierd eh?
[Magisk] hfam:
I have a suggestion for [MENTION=4470081]topjohnwu[/MENTION], and I don't use Twitter, etc so not sure how to get it heard, but if one of you kind souls would pass it on I'd be eternally grateful.

I use core services primarily to provide root, and block a few apps from detecting root. I have a stock Pixel 2 and do not use TWRP anymore. I just blast the latest full factory image on each month without overwriting user partition, it works great (thanks to [MENTION=6842057]nathanchance[/MENTION] for his tutorial thread).

That said, after I update my Pixel 2 monthly, it has no root, so I go into MM, it sees Magisk needs to be installed and I do a boot.img update using the latest boot.img.

My suggestion:. In MM settings, we have 3 channel options: Stable, Beta, and Custom. It would make things much easier and safer to back out of a version for us who don't use TWRP by having a 4th option;. Previous Stable Major Version: That way, if I update to, say, to 19.0, or 19.1, and it causes issues, we could use MM to simply do a boot.img reinstall to 18.3 from the same factory image. Right now that isn't an option for me as I have no way to create a custom link that would take me back to any previous version, so I cross my fingers and hope its going to work. So when Stable becomes the latest, and I flash it, I have no way to regress to last stable that I'm aware of.

Perhaps someone has an alternative to do this process. It's be great if it could be added to MM though, a great safety net for those of us who don't install or use TWRP.

I hope I was clear, thanks for reading, any and all suggestions are welcome! Hoping [MENTION=4470081]topjohnwu[/MENTION] hears my suggestion too, and thanks again!!
[Magisk] grahita:
would you tell me how to repackage the manager?
[Magisk] bafforosso:
Settings > Hide Magisk Manager

You should also follow the advice and try the suggestions in this great guide by didgeridoohan : https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] jcmm11:
Keep a copy of the modded boot image as a backup. You can keep 1 or 2 versions back (or more if you want). Then, if you want to regress, just choose the appropriate saved boot image.
[Magisk] Swierk:
Updating from 18.2 to 19.0 require of reinstallation of all modules?

Sent from Xperia Z5, stock rom 7.1.1, 32.4.A.1.54, Magisk 18.2
[Magisk] triathlete66:
not necessary
[Magisk] Swierk:
ts-binds v1.1 - someone got this module working?

from 18.0 stopped working. On 17.3 was working flawlessly

Sent from Xperia Z5, stock rom 7.1.1, 32.4.A.1.54, Magisk 18.2
[Magisk] Ferr1s:
Hmm as I read that there is a new magisk version, I downloaded it and tried to install. It didtn work. the 19.0 was not recognized by magiskmanager.

so I tried to install the 18.1 again the installation fails too.

here is the log:

- Copying image to cache

- Device platform: arm64-v8a

- Existing zip found

1038+1 records in

1038+1 records out

1063528 bytes (1.0MB) copied, 0.018748 seconds, 54.1MB/s

- Unpacking boot image

MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]

No boot image magic found!

! Unable to unpack boot image

! Installation failed

anybody knows what the problem is?
[Magisk] :
Bon appétit !
[Magisk] jcmm11:
For starters need FULL install log (if you used TWRP it's probably still sitting in /cache/

Also information like what device? What ROM? If custom, what kernel?

What do you have currently installed?
[Magisk] Ferr1s:
OK here the full LOG:

06-21 00:03:39.720 610 610 I Magisk : * Creating /sbin overlay

06-21 00:03:39.721 610 610 E Magisk : linkat charger->charger failed with 18: Cross-device link

06-21 00:03:39.735 612 612 I Magisk : * Device API level: 28

06-21 00:03:39.735 612 612 I Magisk : Magisk v18.1(18100) daemon started

06-21 00:03:39.745 612 613 I Magisk : ** post-fs-data mode running

06-21 00:03:39.745 612 613 I Magisk : * Initializing Magisk environment

06-21 00:03:39.746 612 613 I Magisk : * Mounting mirrors

06-21 00:03:39.747 612 613 I Magisk : mount: /sbin/.magisk/mirror/system

06-21 00:03:39.747 612 613 I Magisk : mount: /sbin/.magisk/mirror/vendor

06-21 00:03:39.747 612 613 I Magisk : bind_mount: /sbin/.magisk/mirror/bin

06-21 00:03:39.748 612 613 I Magisk : * Setting up internal busybox

06-21 00:03:39.766 618 618 I Magisk : Magisk v18.1(18100) logger started

06-21 00:03:39.786 612 613 I Magisk : * Running post-fs-data.d scripts

06-21 00:03:39.787 612 613 I Magisk : * Mounting /data/adb/magisk.img

06-21 00:03:39.845 612 613 I Magisk : * Running module post-fs-data scripts

06-21 00:03:39.845 612 613 I Magisk : * Loading modules

06-21 00:03:39.846 612 634 I Magisk : * Starting MagiskHide

06-21 00:03:39.847 612 634 I Magisk : hide_utils: Hiding sensitive props

06-21 00:03:39.847 612 634 E Magisk : sqlite3_exec: ù·ç÷¹

yes I used TWRP on Mi8 with LineageOS Official 16.0. Before I tried to update to magisk 19.0 all went well for me with magisk 18.1

Kernel idk... just installed the LOS, gapps and magisk 2 weeks ago or so. 1h ago I downloaded 19.0 from the magisk homepage and flashed it with twrp.

after reboot magisk manager didnt recognize any magisk on my device. the log here is already the try to install 18.1 again
[Magisk] AndrzejDwo:
I had the same issue updating from 18.2 to 19 on Samsung SM-G950F. I ran Magisk uninstaller and than I couldn't install Magisk at all. I had to reflash the kernel to make it work. My recovery install log is somewhere around 10 pages back...
[Magisk] JudgeDread11:
I'm not great at this, but did you update Magisk Manager as well?
[Magisk] Ferr1s:
I didnt have to. I was already on 7.1.1

so without magisk my root is gone ?

edit: yea , root is gone. so magisk disappeared and I cant install it anymore :X
[Magisk] IceHotKilla:
Magisk v18.1 and v19 is uninstalled by itself after every reboot.

Any ideas? I'm running on LineageOS 15.1 Oreo.
[Magisk] jcmm11:
That's not the install log. That's a Magisk log. The install log would be in /cache/recovery/ You want the TWRP log. I don't run LOS or an Mi8 so hopefully someone here does. I suspect, but don't know, that the Mi8 is more likely to be the issue than LOS, meaning if there's an issue it's likely to occur no matter what ROM you run. But that's totally a guess on my part and I may be completely wrong.
[Magisk] n756gkj:
I installed LineageOS 15.1 + Magisk 18.1 on a new Samsung S9+/Exynos.

Smooth install -- no issues at all.

One question -- I know it's 'in here' _somewhere_ already, but digging it out of 3254 pages (wow!) is ... challenging:

With LOS stable updates, flashed from TWRP, is it necessary/recommended to RE-flash Magisk each time? I'm not clear if the procedure is at all difference than Magisk + STOCK rom flashes, &/or if the presence of the installed MagiskManager app changes anything.
[Magisk] hfam:
Heya [MENTION=4487388]jcmm11[/MENTION], thanks for the reply!!

At first I thought "Duh, why didn't I think of that?!?", but I don't think that would resolve the issue.

The problem would be that you cannot regress the system update. In other words, once I go from March to April security update, I cannot use a patched_boot.img from any other build than April.

So, hypothetically, when Magisk 19.1 goes to Stable, say, mid-April, when I update my system to May Security Update, I will have no option but to update that May build boot.img with Magisk 19.1 via the MM. I cannot go back and apply 18.3 via MM if 19.1 goes wrong because I can't use a March Security Update patched_boot.img on April or May Security Update.

However, if MM had that 4th option, I could then use my factory boot.img from May and reinstall 18.3 to that current May boot.img, reflash it, and be back to good.

Am making sense? I'm working off the premise that once I flash my Pixel 2 to the latest security update, I cannot use a patched_boot image from a previous OS security update, say, March or April. Is this correct? If not, and I can use a patched_boot.img from any previous OS version (i.e. a previous month's security update, etc, not a full OS version), then I'm great to go!

Thanks again for the reply and clarity on using a previous patched_boot.img would be much appreciated!!
[Magisk] edzamber:
Announcement

Magisk Modules Remover and Magisk Modules Disabler updated to work with Magisk 19+

https://xdaforums.com/showthread.php?p=76208281

Enjoy [emoji6]
[Magisk] jcmm11:
You should be able to use a previous kernel. Try it and find out.

If you use a custom kernel you can definitely use an older kernel. Kernels, generally speaking, aren't tied to a specific release. If you're running 9.0 then any 9.0 kernel should work, although I wouldn't expect it to work on 8.x, or anything greater than 9.0 (although 9.1 (if it existed) might be ok, but I wouldn't count on it).

Another possibility is to get yourself a copy of Franco's kernel manager. It now has the ability to flash pretty much any zip (that doesn't modify system or vendor. If you want to do that "there be dragons" to quote the app) as well a backup and restore kernels. Now you need boot to run it so. Flash old kernel, boot phone, start FKM, flash current stock kernel - but don't reboot. Flash Magisk version you want, reboot. You now have current kernel with desired Magisk.
[Magisk] hfam:
Brother, you are awesome! You nailed the essence of my questions, and I'm super excited to learn that an earlier kernel (within OS versions of course) is fairly independent from the rest and can be booted to. Makes perfect sense in light of a custom kernel working!! I'm wired for redundancy due to my career so oddly enough I have all my previous boot.img and patched_boot.img files, sorted by month, for all of Pie 9.0 and Magisk 17 on. SUCH great news, you have no idea how happy you you made me, huge sigh of relief.

I am DEFINITELY getting Franco's kernel manager too, thanks!!! Brilliantly applied to my issue, great thinking and again, eternal thanks for your thoughtful and knowledge-packed replies brother!!

Man I just learned a LOT, so happy!!
[Magisk] xunholyx:
Flash your stock boot.img

Flash the magisk.zip in twrp. It contains the Magisk Manager apk and will patch your boot.img

You won't lose any modules that way (except for Vanced YouTube afaik)
[Magisk] jcmm11:
I'm just curious why you don't use TWRP at all anymore. You do know that you don't have to install it and that you can just boot it via fastboot anytime you need it (which is the way I do it)?
[Magisk] hfam:
Before my Pixel 2, I owned a lot of HTC phones, no A/B stuff, and it was pretty clear how it all worked and I used TWRP religiously for nandroid backups and chainfires SU. Got the P2 and TWRP looked a bit too easy for me to make a mistake, still don't quite understand at the level I'd like, how A/B boots work, AND had a brick RMA incident the day I got the phone using what was at the time the Magisk instructions how to update 14.x. Wanted one to take ota, pause it between download and install Magisk, reboot...vague mems but the bricking to RMA level is still fresh and stings.

Found d [MENTION=6842057]nathanchance[/MENTION]s tut thread on rooting Oreo with Magisk and that method hasn't failed me since, no TWRP required. I guess I figured since I don't miss it, and how it now works with A/B is unclear to me with me with enough specificity to make me comfortable, why bother and stress out. If it ain't broke don't fix it kinda I guess

I am aware of booting to TWRP from an image using platform tools is possible, but just haven't had to deal with it to this point, and aside from what I learned today(thanks again!!), I understand how, and more importantly, why, that process is foolproof...for me anyhow.

I suppose I should at least work on getting comfy with booting to TWRP via platform tools, make use of the options it'd provide. Know of any Tut's on that process that is thorough in explanation? I'd love to learn. Also, grabbed FK on your recommendation, that looks incredible, already made a backup of my current April kernel running Magisk 18.1. no time like the present! That app kills for the price. Almost seems too easy!!!

Also, If you have a source where I can educate myself on using TWRP image to temp boot, etc, I'd love to learn it. Looking for a step by step that assumes nothing would be my preference.

Thanks again [MENTION=4487388]jcmm11[/MENTION], I really appreciate the interaction and knowledge!!
[Magisk] basily:
OK, I don't know where else to ask this, and I'm not even sure it's related to Magisk, but I suspect that it is.

I'm aware that an OTA won't install if you have any system modifications, however, is it possible that as of late, an OTA won't even download? I didn't think that I had modified my system at all, but for many months now, I have never received any OTA's even halfway into the month, and it's my understanding that the "check for update" now works. I don't believe that it's carrier related because my wife has the exact same phone (P2XL) and same carrier, and she already has the April update, while my phone insists that "Your system is up to date". We're both on Mexican Telcel, she, however is in Canada at the moment, and I am in Mexico. I don't know if that matters, but I've gone so far as to use VPN and spoof my GPS location, with no success.

So, this is why I'm wondering, if, maybe my Adaway app (or something else I haven't thought of) changed the hostsfile on the system partition (before I enabled systemless hosts on Magisk) and if this system modification is being detected to leave me out in the cold for OTA's.
[Magisk] martyfender:
Disclaimer, I do not own any Pixel devices. However, I believe that updating the hosts file without the systemless hosts module enabled would be the reason.

I think you can reflash your system without wiping data by removing the -w flag, if I am not mistaken. Those that own these devices please clarify if I have anything wrong and give detailed instructions.

Thanks
[Magisk] basily:
Yeah, I tried this. Flashed the March update (without the -w flag), didn't re-install magisk, and it still won't give me an OTA. I was going to recruit google's help, but even the "Tips & support" won't open. It's just sits on a blank screen that says "Help" at the top, blank screen and the "wait" circle spinning and spinning, eventually giving out to "Google Play services isn't responding: close, wait or send feedback".

I'll say it before anyone else can... I think I might need to resort to a full wipe unfortunately. This and a couple of other minor flaky things happening... :(
[Magisk] martyfender:
If I am not mistaken, you can also download the full OTA update installer and apply it, instead of the settings, system update route. I'm not sure, but that may be carrier dependent, also?
[Magisk] xunholyx:
Download the twrp.img and place into your fastboot folder.

Then: fastboot boot **drag and drop the twrp.img here**

Or, rename the .img to something short and easy to type out (I'll use twrp here for simplicity), and:

fastboot boot twrp.img
[Magisk] hfam:
No kidding, that easy? Geez, now I feel a bit foolish I haven't tackled this earlier!

Thanks [MENTION=4987085]xunholyx[/MENTION], that's perfect. Appreciate the assist. I'll go grab the appropriate TWRP distro and give it a go. Couple of questions that may seem obvious, but keep me up at night when I stray from what I know:

- Booting into TWRP this way won't hose down any of the A/B boot stuff, correct? (I really need to go and find out how and why A/B boots works so I can stop stressing about it!)

- This is truly a temp boot that alters nothing about the phone by just booting into TWRP. i.e. it doesn't make any changes, even when I choose "done, reboot". As far as the phone is concerned, it has no idea and TWRP leaves no trace of itself, correct?

- If I use TWRP in this way to, say, flash a Magisk.zip to a previous version, again, it leaves no trace of itself, so when I reboot the only change the phone sees is the Magisk flash, again, no trace of TWRP, no further requirement to now be tied to TWRP, correct?

Sorry for the extra questions, may sound a bit over cautious and the answers are probably obvious to many, but I'd rather ask these upfront than do something I'd regret later because I didn't ask. ;)

Thanks again for the assist!
[Magisk] xunholyx:
My answers are in red above
[Magisk] curiousrom:
I don't see anything red in the XDA app. ;)
[Magisk] xunholyx:
lol

I don't use the app. I always use my PC or a the Chrome browser on my phone.

I'll edit my post so there is a space between the questions and answers, and I'll mark them with "Q"s and "A"s to make it easier for people using this or other apps that don't get the red text.
[Magisk] curiousrom:
BTW your red comments nested in a quote are themselves not easily quotable as you can see in my post above
[Magisk] xunholyx:
I've edited my post to compensate for those using the app.

Thanks for bringing it to my attention.

As far as quoting it though, I'm not really concerned about that. It isn't something I even thought of. It's just an easier way for me to answer multiple questions.
[Magisk] basily:
Well, yeah, but the point is i need a computer to update, which is a pain if i plan to be away from my computer for a while... Flashing the full firmware or just the OTA, is pretty much the same thing for me. I'm just going to have to do a clean flash unfortunately.
[Magisk] xunholyx:
Personally, I don't flash anything (anymore) without a computer near by. Even when I had TWRP on my phone. If you run into any problems, it's good to have fastboot nearby to get out of trouble.

I flashed something (I don't remember what) onto my HTC 10 once on my way to work that didn't go as planned. I ended up being without a phone for the day until I got home.
[Magisk] jcmm11:
To learn about A/B partitions start here https://xdaforums.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123

And just to reinforce what [MENTION=4987085]xunholyx[/MENTION] said, yes all your assumptions were correct. Just booting TWRP leaves no trace of TWRP on your phone and doesn't hose anything as far as A/B partitions go (just don't mess with the A/B options - leave them at default).

---------- Post added at 09:33 PM ---------- Previous post was at 09:26 PM ----------

This - 100%

If you routinely flash stuff without a computer handy eventually something will happen that will make you regret it. This coming from someone who used to routinely flash stuff even though I didn't own a computer at the time and had to jump through hoops to get access to one when I absolutely needed it. I did it because I had no option at the time. Didn't like it, and did eventually run into trouble (and I'm very good at usually avoiding trouble).
[Magisk] hfam:
Thank you so much for taking the time to offer your help and knowledge. Once again, Im grateful and relieved to learn not only the how, but the why, of functions that weren't really clear to me. You've helped immensely, and even if it may seem a small thing to some, it's a real big deal to me.

You, [MENTION=4487388]jcmm11[/MENTION], [MENTION=4667597]Didgeridoohan[/MENTION], [MENTION=6842057]nathanchance[/MENTION], [MENTION=8126387]martyfender[/MENTION], and all the rest of the folks here who selflessly and endlessly offer their assistance make this one of the best forums anywhere, that's a fact.

I can't express my thanks enough, what a great place you've all created.

---------- Post added 07-04-2019 at 12:02 AM ---------- Previous post was 06-04-2019 at 11:49 PM ----------

Thank you again! I'm on my way to that link right now!

Excellent advice on a PC, I wouldn't dream of doing anything of the sort without platform tools by my side.

MAN I feel good today, thanks again all!
[Magisk] Prothean:
Hi, I am using latest magisk 19 and latest manager on my S6 edge. Everything works fine but there is one thing that's really bugging me: every time my phone reboots magiskhide is not working and I have to disable-enable it and clear google play services data in order to pass safetynet. Does anybody know a fix for this?

Unfortunately, the latest canary build did not solve my issue. I am also already using the modules magisk hide prop and safetypatch.
[Magisk] martyfender:
I would suggest trying the latest Canary build, that may help. The latest, v19003, has some Samsung fixes in it. Also, Magisk Hide Props Config module could help. If the above suggestions don't help, then I am not sure.
[Magisk] Tecalote:
[MENTION=4667597]Didgeridoohan[/MENTION]

I have rooted Mate 9 /EMUI 9.

Patched recovery_ramdisk.img with Magisk Beta v19, booted with Vol+ and using newest Magisk Manager.

Using this method: https://topjohnwu.github.io/Magisk/install.html#emui-9

Installed Busybox module by osmosis.

Everything working fine - thanks to topjohnwu :good:

The first few times I must use the Button combination to boot into the rooted system, after that I can restart phone as usual without Vol+

Just one question:

If there will be a Magisk Update (stable v19 or v20...) - is it always required to patch and flash the recovery_ramdisk manually, or will Magisk recognize the patched recovery_ramdisk and I can use Direct Install method?

Thanks!
[Magisk] Didgeridoohan:
Update through direct install. Updating by manually patching recovery_ramdisk might actually mess up your Magisk setup.
[Magisk] onewaydown:
Hello wonderful folks. Does anyone here use Vudu? I thought it used to work with Magisk, at least to watch videos. Maybe I'm remembering wrong. But I get an error that rooted devices aren't supported. I've hidden Magisk Manager, set Magisk to core mode, and added Vudu under Magisk Hide but still no go. Anyone have an idea how to get it working?
[Magisk] Cwiara24:
Hey. I have a problem with magisk installation, I have version 18.1, I want to update it to version 19, everything is uploaded, but later in the manager it crashes the message that magisk is not installed.

Android Nougat Samsung G935F (s7 edge)

ROM: AP_G935FXXS2DRDI_CL12365438_QB17789087

log from magisk manager

:confused:

Thank you for your help

Best regards
[Magisk] garylawwd:
Use the uninstaller to delete Magisk first and then just flash v19 in recovery
[Magisk] mdrda:
My device suffers from a boot freeze because of a bad module. Cannot use TWRP and don't have module like Magisk Core Only installed for recovery.

Rooted system cannot be booted because of bad module. Non-rooted system boots fine but without root, i.e. no joy writing to FS under /data.

My device LYA (Mate 20 Pro) uses Magisk patched recovery image root method - root is gained by booting through recovery.

Does a Magisk edition exist or can easily be built which will either skip loading custom modules or delete them during boot? After successfully booting rooted I would remove conflicting module and flash a standard Magisk.