yashsingh1/xdaforums huggingface dataset:
[Magisk] JudgeDread11:
I had that issue a long time ago, a whole bunch off versions ago. For me it was caused by a corrupted magisk database. I deleted the database and magisk manager app data. Then set everything up again and that solved it for me.

---------- Post added at 03:03 PM ---------- Previous post was at 03:02 PM ----------

You can use the TWRP file manager.
[Magisk] Sarandeep Singh:
Solved the issue !!

Deleting busybox-ndk will not solve this

The fix is to uninstall magisk by flashing uinstaller.zip and then fresh install magisk by twrp. ?

I request you all to don't flash the busy box android ndk module from magisk its not stabel with new security updates of android if u do then you might lose root and magisk.
[Magisk] Didgeridoohan:
Now, that's just wrong... There are many users of [MENTION=4544860]osm0sis[/MENTION] Busybox with no issues at all. On all the latest updates... All we know is that you have experienced a hiccup that might or might not actually have had anything to do with the Busybox module.

Don't make such a statement unless you for sure can say there's something wrong, and if you can please make sure to share that info with [MENTION=4544860]osm0sis[/MENTION] so he can fix any potential issues.

Best way to find out is to install the module again and also save the installation log while doing that. If things work this time we know it was a temporary thing on your device, if it doesn't work you might have more info for us in the saved log.
[Magisk] dope77:
If didn't work for you, it doesn't mean it won't work for others. Keep your opinions to yourself, unless u got some real proofs based on testing.
[Magisk] kiwigi:
S7 exynos install_Oreo

Hi All

I hope you can bear with my question about the install :D

Just to be sure, is the instruction below what applies for my phone? As under Samsung there are various sections. As allays a bit nervous when it comes to install as it is my daily driver.

https://topjohnwu.github.io/Magisk/install.html#instructions

Thanks heaps in advance:)
[Magisk] lividhen99:
so, if i were to flash magisk on a nook color running cm11, would i need to remove the native root access first? i remember hearing something about that years ago, but there is nothing now. any help would be apprecieated.
[Magisk] Artim_96:
Are you talking about CM11 as in CyanogenMod 11/Android 4.4?

Well first of all you should check back with the dev of the kernel even supports all patches mentioned in the first post of the announcement thread.

But if Magisk could work, yes you will need to remove existing SU solutions.
[Magisk] Longerski:
I have Pixel 3 and Q beta and I used this tutorial to edit the build.prop.

"Create a folder in /data/adb/modules. Put an textfile called module.prop into it containings lines like

<br />

and one called system.prop like this

<br />

<br />

Then reboot and enjoy!"

And if I want to delete something from the build.prop in the original location , how do I do it?

So the build.prop in the original location will not be loaded and only the new build.prop will be loaded?

Thanks.
[Magisk] Didgeridoohan:
In the same module, put this command in post-fs-data.sh (or in service.sh if it doesn't seem to be working):

resetprop --delete ro.config.low_ram

Replace "ro.config.low_ram" with whatever prop you want to remove.

More details on resetprop here and you'll find more if you run the command in terminal with the --help option.

You don't need to actually edit the build.prop file. All that matters are the loaded values, and Magisk will take care of that for you.
[Magisk] Spaceminer:
Does anyone know how to solve this error? I'm trying to patch a dtbo.img manually, which Magisk should be able to do. This is the only output and I'm not sure what could cause it. The dtbo.img is only ~2mb, and it doesn't run out of memory when patching a 32mb+ boot.img, so I don't know what gives.

:/data/local/tmp # ./magiskboot dtb-patch dtbo.img

Loading dtbs from [dtbo.img]

Found fstab in dtb.0000

Found block [vendor] in fstab

Found block [system] in fstab

malloc failed with 12: Out of memory
[Magisk] Mikes:
Will Magisk be supported on LOS based ROMs on Galaxy S10 device family? Right now the only option we have is AddonSU.
[Magisk] palmbeach05:
Do you have twrp? Flash magisk. That simple. There's your support
[Magisk] Mikes:
Yes, we have TWRP but it's not as simple as flashing the zip file, it's system-as-root.
[Magisk] palmbeach05:
Flash magisk and get systemless root. Thats the purpose of magisk. Is magisk failing to root s10?
[Magisk] Mikes:
Of course, why would I write here if it worked. It kind of works on stock OneUI when you patch AP file and flash Magisk to the recovery partition but you cant do that on LOS since Magisk doesn't support it at the moment. This device doesn't use ramdisk so the standard solution won't work.
[Magisk] vettayyan:
I used to flash TWRP and flash Magisk V19.3 .. I came up with these errors.. Even I try to flash via Magisk Manager.. Both bounced back with this error.. I couldn't exactly locate this error.. That's why I'm sharing here to look for a solution!!

I'm on OOS 9.0.5 Stock Rom running in OP 3T..
[Magisk] ashyx:
These are all different unrelated errors.

Can you mount system from the mount options in TWRP?

Is the zip corrupt, have you tried disabling zip verification in settings?

Finally as it states your boot image format is not supported or is modified/corrupt in some way.

Does it unpack with AIK kitchen by osm0sis?

You really need to post logs from twrp and Magisk.
[Magisk] martyfender:
[MENTION=4875203]vettayyan[/MENTION] According to your last post in the linked thread, you managed to solve your issue?

https://xdaforums.com/showpost.php?p=80113098&postcount=1610
[Magisk] GioGr:
On Kenzo Pie ROM I get this problem

I download modules and install all fine no but

These unremovable notifications that the modules I installed are downloading and only with force stop or reboot they go away

Minor but kinda triggers me so yea.

thanks for this awesome program ?
[Magisk] palmbeach05:
Zip download for recovery install or install from magisk manager?
[Magisk] GioGr:
All from manager
[Magisk] vonDubenshire:
Since I started flashing Magisk without TWRP I have enjoyed rooting so much more when tinkering with stuff. No more messing up with too much tinkering.
[Magisk] kiwigi:
If I want to change country at the same time as flashing magisk v19.3 , can I use " CSC" instead of "HOME_CSC" (As per instructions)?

TIA:)
[Magisk] ashyx:
Not sure that actually makes sense.

The whole point of a custom recovery is exactly that 'recovery'

It gives you a further layer of protection in case things go wrong if you do tinker. All it requires is a simple backup plus you have other options for fixing things.

Now if someone is daft enough not to create a backup before said tinkering then that is their own silly fault. :silly:
[Magisk] Bringer1:
After installing Magisk 19.3 on my Oneplus 3 (9.0.5 16_190731) there is an bootloop direct after showing the shell.

"system has changed. reboot"

Edit...

Done, by full new flash
[Magisk] zbysogi:
After doing apps update I installed youtube by accident and I shouldn't have done it cause I'm using YT Vanced and I'm not sure it caused it but I'm back to ctsProfile: false and props command doesn't work in Terminale emulator :/
[Magisk] Hyflex:
Hi,

So I was trying to install my OTA update and I restored images but the installation kept failing so I uninstalled Magisk completely however the installation still failed...

I accidently restarted my phone and as such I have lost magisk... How do I get it back because now in TWRP Recovery it is all encrypted.

But before I do that I ideally want to install the OTA update, why is it failing to install? I have only installed Magisk and various modules...

Any help would be appreciated!
[Magisk] Artim_96:
Well, TWRP for your phone should support encrypted /data partition. Otherwise that's something you should discuss with the maintainer.

The OTA might be installable now if the stock boot image was restored otherwise you need to either restore it out get a full firmware image and flash that.

But why it failed probably nobody can explain without any logs or if it's a known OEM specific problem
[Magisk] Didgeridoohan:
Do you have any modules installed that might have caused issues? If so, take a look here:

https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc

If not, you might have something else going on but it's practically impossible to tell from the information given. Take a look here:

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

Another good place to look for info/help would be your device's forum. If it's a device/ROM specific thing you'll likely find others with similar issues and possibly a solution.

Sounds like you might have enabled Core Only Mode. Make sure that it's off and try again.

Usually you need to have both stock boot image and recovery installed for OTAs. More info:

https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
[Magisk] zgfg:
Are you sure that OTA will work for you with TWRP - it depends on the phone manufacturer, you may need to restore complete stock firmware before trying with OTA (there might be even a risk to brick the phone, System downloads the OTA package and reboots to stock Recovery to install OTA)

Such things are not part of Magisk, you should consult forums and threads specific to your phone/model/firmware to find info about the appropriate TWRP for your phone, conditioms and procedures for OTA, etc
[Magisk] GioGr:
I found the problem that results in that buggy notification

It's when u download to install at the manager but when an earlier file is large and a newer one is small

They will install when downloaded no problems there but that notification mess happens.

Edit:A large one is YouTube and a small one init and you'll get this also if your download speed is not epic :P

Edit2:lies YouTube didn't install probably cuz another install was happening at that time. Realized it after reboot.
[Magisk] lividhen99:
So... Um... Does anyone know who managed the nook color kernel? Or, what kernel it even uses with cm11? I can't find any info. Anywhere. All the usernames on the boot screen are marked as inactive developers.
[Magisk] lividhen99:
Here's the screen,just in case I'm missing something. But I thi k the people on here are just the ui.
[Magisk] DenyDarko:
Oh? [MENTION=4667597]Didgeridoohan[/MENTION] became purple I see.

Well deserved. Awesome
[Magisk] aer0zer0:
Moderator is a blessing/curse. Not sure if I would want it, lol
[Magisk] Artim_96:
That's something you should definitely take to your devices forum. I'm already surprised enough that someone still has a device that's useable that can only be used with 4.4. but if the ROM is that old you might be out of luck.

You can always just try it out and like I said as far as I know you still have to always remove existing root methods, but other than that, there might not be much of support possible
[Magisk] lividhen99:
Yeah, it's just an old tablet I have. I Don't need magisk, but I would have been cool! ?
[Magisk] Andrew-J-Larson:
myStudentAid still detects root (while all other SafetyNet apps don't)

Here's what I've done so far on my device (and what device it is):

Device: Razer Phone (cheryl)

Recovery: Lineage Recovery (modified with Magisk for both A/B partitions)

OS: LineageOS 16.0 is installed (+ MindTheGapps & Magisk Manager)

OS Build:

lineage_cheryl-userdebug 9 PQ3A.190801.002 2ab06675d3

Android Version: Pie (9.0)

Magisk Build: Stable v19.3 (with Magisk Manager 7.3.2 installed)

Magisk Modules Installed:

- Busybox for Android NDK

- MagiskHide Props Config

- Single User Mod

- Youtube Vanced black themed - Magisk Repo​

In order to pass the "ctsProfile" I had to modify the device fingerprint, courtesy of the "MagiskHide Props Config" module. After applying the Razer Phone Oreo fingerprint:

razer/cheryl/cheryl:8.1.0/OPM1.171019.011-RZR-180803/6033:user/release-keys

, it was passing the "ctsProfile". All apps that were discovering root/not working because of it, were working under MagiskHide. The only app now that is somehow still detecting root is myStudentAid from the Google Play Store. I have tried repackaging the manager, clearing the data in the app and making sure it was under MagiskHide before starting it again. Yet it still gets to some weird connection problem which I feel is still some sort of root detection block, since the app is having no problems (that would have been reported to the FAFSA main twitter). Before repackaging, it would actually display the error

However, after Magisk Manager was repackaged, it would only show this error,

Now... I'm no expert, but my assumption here is that some form of network based scanning/detection is being used on the app, but I can't say for sure. And I did try this both with wifi only, and data only, to make sure it wasn't a network problem on my side.

Attached should be the logcat of me trying to open the app once, with it not working (but running MagiskHide with Magisk Manager in the repackaged state, as "Manager"). I ran the following command from ADB on my PC:

adb logcat -v long > myStudentAid_08-25-2019_logcat.txt

and in case you need it, the app is under the package name:

com.fsa.mystudentaid

Thanks for any help in advance.

(logcat was too big, so it's posted here via Ubuntu Pastebin)
[Magisk] palmbeach05:
I recently dug out my old atrix 4g. Has a 4.4.4 rom on there, and magisk works good there too
[Magisk] dope77:
hey, i have this app installed https://play.google.com/store/apps/details?id=com.arcai.netcut&hl=en ,after granting su permission, magisk manager becomes unresponsive and then crash,only face this problem with this app.

also tried using it on a different device,same problem,manager becomes unresponsive then crash

any ideas?
[Magisk] guest4711:
This app is probably flooding MM with su requests. Have a look into Magisk log. (Perhaps switching off su notications abd logging this app in MM->su could help a little bit.)
[Magisk] dope77:
cheers mate,that did the trick
[Magisk] treetolber:
Suddenly safety net stopped passing. The only thing I added since it was passing was there substratum module. Could that be it?
[Magisk] guest4711:
Indeed.
[Magisk] treetolber:
So I removed that module and the substratum app, then rebooted and still no pass. Going to try removing all modules, uninstalling magisk the reflashing magisk.

---------- Post added at 09:42 PM ---------- Previous post was at 09:10 PM ----------

That seemed to work. But after bringing back the modules one at a time safety net breaks after flashing the Edxposed modules. They have worked before. I added the Xposed app to hidden but still fails safety net. Has anyone else gotten the Xposed to work with safety net?
[Magisk] wilsonhlacerda:
S4 Active here running LOS16 encrypted and Selinux enforced. All fine. See detailed installed apps on screen shots.

And I'm NOT playing with white/black list on EdXposed (but this can be useful to help hide EdXposed from rooting detect apps).

I'm not Magisk hiding EdXposed app neither using Magisk Hide Props Config module (but this can be useful depending on your ROM).

Don't you have that Magisk bug that hide only works after toggling Magisk Hide on its settings after boot? I do have it, thus I put a tiny scrip to toggle automatically on boot.
[Magisk] treetolber:
Thanks. I tried a different version of the Xposed modules and manager and everything is great now.
[Magisk] kamieniarz:
I have an issue with my Nexus 5. I've flashed LineageOS 15.5 and Magisk 19.3. SafetyNet is true but after I grant SU privileges (to any app(s)) SafetyNet changes to false... Any idea how to fix it?
[Magisk] guest4711:
Toggle MagiskHide off and on again and see if it helps.
[Magisk] kamieniarz:
it didn't help
[Magisk] guest4711:
So have a look onto [MENTION=4667597]Didgeridoohan[/MENTION]'s fine manual/faq: https://www.didgeridoohan.com/magisk/MagiskHide#safetynet
[Magisk] Lauriso:
Is this the right place to ask whether a certain feature could technically be made into a Magisk module?
[Magisk] martyfender:
If you are passing basic integrity but failing the cts profile, then installing the MagiskHide Props Config module may help you if you apply a certified fingerprint. If you are failing both basic integrity and the cts profile, then you need to look elsewhere to figure out where the problem lies.
[Magisk] Meepaco:
I seem to loose root whenever magisk manager gets killed by LMK, is there a way to prevent LMK from killing magisk/components in the background?

Not optimized in battery settings, op6 9.0.8 if that helps.
[Magisk] ktmom:
Look here
[Magisk] paarnoutse:
Especially for OnePlus devices (OxygenOS), in addition to setting Battery optimization OFF for Magisk Manager, also lock Magisk Manager in your 'Recent Apps' list.

See https://xdaforums.com/showpost.php?p=78588761&postcount=7 for background info and details.

(although described there to prevent that Titanium Backup would be killed, the reason and solution is applicable for any app that you don't want to be killed, incl. Magisk Manager, etc.).
[Magisk] Meepaco:
Thanks, will see if this helps
[Magisk] Custard_141:
I have a rooted s9+ using Magisk 19.3. I keep getting locked out my snapchat, the only apps I have that could be making a difference are:

- Disk digger

- Dumpster

- Simple reboot

- Tasker

- GPS + joystick repackaged called Flashlight

My modules for Magisk are:

- libsecure_storage companion for Samsung devices

- Magisk manager for recovety mode

- Smali patcher

- Youtube vanced (Not sure why this would trigger it?)

I previously had adaway + titanium installed but have since removed to see if they were causing issues

Does anyone know of a solution?
[Magisk] palmbeach05:
Just to point something out, disk digger and dumpster essentially do the same function
[Magisk] elliwigy:
probably been mentioned already but nvidia shield tv on 9.0 update doesnt work with Magisk anymore.

the firmware only contains system vendor boot and recovery.. no vbmeta or other partitions..

magisk shows it patches both boot and recovery but when flashing or attempting to boot from fastboot to either one it just sits on the nvidia logo and never does anything..

further more i tried using magiskboot to unpack the boot and recovery images. when it unpacks in the dir is kernel, ramdisk.cpio, header... in the details it says it contains ramdisk in gzip format.. when trying to decompress ramdisk it says its not a valid gzip format..

long story short magisk app shows successful but then doesnt work and manually it gives errors trying to decompress or modify boot or recovery.

I dont have logs bcuz of course magisk app reports no errors when patching..
[Magisk] Didgeridoohan:
[MENTION=4470081]topjohnwu[/MENTION] rarely visits the forums anymore. Better to post at GitHub:

https://github.com/topjohnwu/Magisk/issues/1750
[Magisk] elliwigy:
ill try later lol thought maybe someone here would have an insight..

truth is, i dont want to sound like an idiot on github lmao

someone said they posted on githib n he basically shot em down n told them it was due to modules but it was a clean install with no root or magisk to begin with lol.. poor guy

he probably didnt explain tho.. was prolly somethin like "shield tv update 9.0 magisk no work" lol
[Magisk] Didgeridoohan:
Yes, that's the exact Github issue I linked. It was reopened, since there was no modules involved (bootloop after OS updates are very often caused by incompatible modules).

The info you've provided here is way more than what anyone's provided there so far...
[Magisk] elliwigy:
oh lmao.. thought was just the main github.. i posted some more details.. hopefully it helps..

i like the pixel and sammy users tryna take over the issue lmao
[Magisk] Tabish0099:
Encrypted Data Partition Issue With Magisk

As we know that latest huawei devices came with encrypted data partition so if we flash a module that cause bootloop we cannot remove that module with twrp using uninmod or mm because data partition is encrypted so kindly modifiy the magisk to install not in system not even in data but /su folder so that if we cause bootloap then we could remove it using twrp or just simply create a module to reboot in magisk core only mode that could be flashed with twrp even with encrypted data partition.
[Magisk] Artim_96:
... Just wait for TWRP to support encryption. It works on almost any other device so why go through the trouble changing how Magisk works if that minor problem should be fixed soon?

Other than that, there is/was a module for Moto devices that moved Magisk to /cache,I think it was called something like F2FS fixer. Don't know if it still works
[Magisk] elliwigy:
i think the issue is the app is reporting success but its not lol.. i had some others confirm trying to decompress the ramdisk.cpio is failing when trying manually with magiskboot.. its saying its not a valid gzip format or something.. maybe nvidia used some other method to compress ramdisk? i think its not patching ramdisk causing it to not boot..
[Magisk] Custard_141:
Yeah, I had disk digger to look for files I lost pre-root and installed dumpster for the protection without deleting disk digger

---------- Post added at 07:13 PM ---------- Previous post was at 07:06 PM ----------
[Magisk] zgfg:
It can be waited forever, it will not come:

It's a common issue for all Huawei, Honor and Mate, running Android 8, 9 and 10.

Not that 'lazy TWRP developers' did not want to implement support for encrypted Data partition and Internal memory, rather it seems that it was not possible to break the AES key

It is only possible (writing from such a Huawei P9 woth Oreo) to format Internal storage (loosing everything from Data and/or Internal) and to overwrite fstab in Vendor partition declaring that e.g. Data is no more encrypted.

However, next reinstallation of firmware (,e.g. full OTA) will encrypt again

Such decryption is not even applicable to EMUI 9.1 (newest Huawei/Mate/Honor Pie firmwares) where Vendor partition is Read Only
[Magisk] Artim_96:
Since when does encryption have to be broken? AES can't be just broken, on any phone. TWRP has to give you an interface for you to authenticate to the secured storage in the SoC so it releases the encryption key. Encryption is still intact. Otherwise you'd have to break encryption on any device in order to be able to use TWRP. So l that would mean much more devices would be unable to be modified that deep. But phones like Verizon phones and Blackberries are pretty much impossible to be modified because they activated protection against flashing any custom software and they keep the keys for unlocking to themselves. Simple as that.
[Magisk] Custard_141:
Any one know?
[Magisk] fathermocker:
In model Samsung J727P (J7 2017 Qualcomm Sprint) J727PVPU6BSF2 July Oreo firmware updates the DEFEX protection in Samsung and breaks compatibility with Magisk flashing :(
[Magisk] Tabish0099:
Actually its not a small issue and i dont think that TWRP could decrypt it but if no one want to modify magisk then no problem just kindly simply create a module that reboot magisk in core only mode and can be flashed through TWRP even data partition is encrypted
[Magisk] Artim_96:
Like I said, there is a module that moves Magisk to /cache. So no need for bigger modifications
[Magisk] Didgeridoohan:
You don't need a module or zip for that. Just create the file /cache/.disable_magisk.

More details:

https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc

Edit: Unless of course you have a device that uses /data/cache, in which case you're screwed...
[Magisk] Artim_96:
I had written that already in the canary channel but maybe you can think of a solution for this one:

There might be some module leftovers in /data that made Magisk uninstall itself and might prevent me from reinstalling it through a patched boot.img. the problem is that I'm running Q beta and TWRP isn't compatible. It can't mount /data and I'm not sure if /cache is mounted right since it's shown empty. Any suggestions how to completely remove Magisk files without having to perform a factory reset or wait for TWRP to support Q?