yashsingh1/xdaforums huggingface dataset:
[Magisk] robintan5566:
Hi, Thanks for the guidance. I have changed to the custom channel. The installation still failed. :(

- Detecting target image

- Device platform: armeabi-v7a

- Existing zip found

MagiskBoot v18.1-3ccac8c3(18004) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/dev/block/boot]

- Unpacking boot image

HEADER_VER [0]

KERNEL_SZ [7283099]

RAMDISK_SZ [2708738]

SECOND_SZ [32955]

EXTRA_SZ [0]

RECOV_DTBO_SZ [0]

PAGESIZE [2048]

NAME []

CMDLINE []

CHECKSUM [c13a84edd37cc57f9c2f036cfd3ac3346630cfac]

KERNEL_FMT [lzop]

RAMDISK_FMT [gzip]

- Checking ramdisk status

MagiskBoot v18.1-3ccac8c3(18004) (by topjohnwu) - Boot Image Modification Tool

Loading cpio: [ramdisk.cpio]

- Stock boot image detected

- Backing up stock boot image

MagiskBoot v18.1-3ccac8c3(18004) (by topjohnwu) - Boot Image Modification Tool

Compressing to [stock_boot_4feb81dde4715972df6473dc0542873cde5de690.img.gz]

- Patching ramdisk

MagiskBoot v18.1-3ccac8c3(18004) (by topjohnwu) - Boot Image Modification Tool

Loading cpio: [ramdisk.cpio]

Add entry [init] (0750)

Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]

Loading cpio: [ramdisk.cpio.orig]

Backup mismatch entry: [init] -> [.backup/init]

Add entry [.backup/.magisk] (0000)

Dump cpio: [ramdisk.cpio]

MagiskBoot v18.1-3ccac8c3(18004) (by topjohnwu) - Boot Image Modification Tool

MagiskBoot v18.1-3ccac8c3(18004) (by topjohnwu) - Boot Image Modification Tool

MagiskBoot v18.1-3ccac8c3(18004) (by topjohnwu) - Boot Image Modification Tool

- Repacking boot image

MagiskBoot v18.1-3ccac8c3(18004) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/dev/block/boot]

HEADER_VER [0]

KERNEL_SZ [7283099]

RAMDISK_SZ [2708738]

SECOND_SZ [32955]

EXTRA_SZ [0]

RECOV_DTBO_SZ [0]

PAGESIZE [2048]

NAME []

CMDLINE []

CHECKSUM [c13a84edd37cc57f9c2f036cfd3ac3346630cfac]

KERNEL_FMT [lzop]

RAMDISK_FMT [gzip]

Repack to boot image: [new-boot.img]

Segmentation fault

! Unable to repack boot image!

! Installation failed
[Magisk] martyfender:
I had just thought of that and updated my original post from yesterday.

Download the older Magisk.zip. open MM and go to the add module area and click the + and choose the older Magisk.zip you downloaded to flash it. That will work but if you don't currently have root, that could fail. If that fails, maybe someone else will have an idea how to do this.

Is TWRP made for your device? If so, that is the best way to flash older versions.

I think this may be the one for your device:

https://twrp.me/samsung/samsunggalaxynote3qualcomm.html

https://xdaforums.com/galaxy-note-3/development/recovery-twrp-3-2-1-1-t3746760

Also, was any newer version of Android released for your device, either officially or unofficially?
[Magisk] meciu99:
I have an issue.

Oneplus 6T with Android 9.0 + Magisk 18

After reboot I'm able to pass SafetyNet, but few hours later - not.. reboot and again I can pass SafetyNet
[Magisk] Tecalote:
This seems to be definitely a Bug of version 18 for some devices. [MENTION=4667597]Didgeridoohan[/MENTION]

I have the same issue on Huawei Mate 9 (MHA-L29 c432 8.0.0.376)

After reboot safetynet okay, some minutes later ctsProfile and basicIntegrity false.

Only one Magisk Module installed: Busybox for Android NDK by osmosis.

After I tried to change Fingerprint with your Hide Props Module, but it didn't help - same issue.

I haven't made Logs yet.

I downgraded to 17.1 and it's solved. Means, it occurs only with v18.

I didn't test canary build.
[Magisk] Didgeridoohan:
It's a known bug (but not the reason behind it). [MENTION=4470081]topjohnwu[/MENTION] has an open issue about it, but unfortunately it's getting spammed with useless "doesn't work for me either" comments rather than anything useful, like logs, a reliable way of reproducing, etc...

Edit: for anyone experiencing this, it should be enough to just toggle MagiskHide off and on rather than go through the hassle of rebooting.
[Magisk] Tecalote:
Yes, ofc. Sorry for not providing logs yet, but I will do.

But [MENTION=3037287]meciu99[/MENTION] made a Log (one post before mine)
[Magisk] Didgeridoohan:
Unfortunately, the log [MENTION=3037287]meciu99[/MENTION] provided is from the stable release, so the log is very sparse. Any bug reports should be done on the Canary debug build to get more verbose Magisk logs. And, a second unfortunately, it's very likely that the issue is occurring because the process monitor in MagiskHide is failing for some reason which in turn means it won't show up in the Magisk log... Someone might have to run a constant logcat to catch whenever the failure happens. That, together with a Canary debug log could possibly show something.

Of course, I'm just speculating, but so far noone that's been experiencing the issue have been able to provide any insight...
[Magisk] jenslody:
If you use a pc you do not need a constant logcat, just a large enough buffer and adb.

Or you place script loke this:

#!/system/bin/sh
rm -f /cache/bootlog.last_log
mv /cache/bootlog.log /cache/bootlog.last_log

logcat -f /cache/bootlog.log

in "/data/adb/post-fs-data.d" or "/data/adb/service.d" and make it executable.

Assuming you have "/cache", otherwise a fix is needed.

And don't forget the script, the log-file can become very large on very long running systems.

I used it to find the cause for a bootloop when bringing Pie to J5.

I can not attach the file with the forum-app, upload spinner never stops, that's why I post the content.
[Magisk] AntholifeV2:
I would have liked to know if there was a Magisk module to display the advanced restart menu (Recovery, quick restart ..) / Otherwise, do you know how to have an advanced restart menu on S9? Thanks. And without Xposed, no customization no? ..
[Magisk] martyfender:
I personally use an app, Simple Reboot, by the famed Francisco Franco.

In the past, on my older Android 5 Nextbook 8, I used Advanced Power Menu.

There are other good choices on the play store.
[Magisk] jcmm11:
+1 for Simple Reboot https://play.google.com/store/apps/details?id=simple.reboot.com

---------- Post added at 01:28 AM ---------- Previous post was at 01:25 AM ----------

Depends on what kind of customization. There are apps and substratum themes out there that allow for customization. That's a word which, on its own, covers a very wide variety of possibilities.
[Magisk] AntholifeV2:
Perfect thanks, and do you know if there are customization modules (eg lol, something that is only a detail, but having the time in the middle of the bar is nice.) Outside xposed?
[Magisk] jcmm11:
If your device/OS is supported https://play.google.com/store/apps/details?id=me.msfjarvis.substweaks has a center clock mod.
[Magisk] 124112:
I have a TMobile LG V20 (H918) that was running on Magisk 16.x, before attempting to update via the app. I chose Direct Installation.

Afterward my device was left in a boot loop.

I cannot flash TWRP back onto my device as instructed by [MENTION=8126387]martyfender[/MENTION] due to the following error:

I do not know what to do from here. I don't know if I have any data left on my phone. All I know is that the bootloader is still unlocked, according to getvar all.

Any advice? I know that the newest versions of Magisk do not work with LG V20, but I don't know why I can't boot into/load TWRP.
[Magisk] andoruB:
https://xdaforums.com/showpost.php?p=78519650&postcount=30040

https://xdaforums.com/showpost.php?p=78521623&postcount=30052

Coming back to my previous issue, I've now tried doing a factory reset on the phone, downloaded again the OTA, and proceeded to do the update, I still get the error screen after reaching roughly 5% of the update process.

I'm getting quite frustrated with this. Is there really no solution for my predicament?
[Magisk] Omitsch:
Is it possible to create a Module that set a fixed image an overwrite the camera input. So every time I open the camera the same picture will appear.

Please can someone write such a Module for Magisk I'll also pay for it.

If you are interested please write me a PM.
[Magisk] PistolSlap:
Rooting not working!

Hello I've been trying to root my Pixel 3 (Android 9, stock rom and kernel) but nothing is working so far. I tried flashing Magisk 18, and Magisk 17.3, and both of them resulted in not necessarily a boot loop, but after the Google boot screen it just rebooted back to recovery. I tried booting several times with the same result. Each time I used the uninstall zip to rescue it.

I also tried flashing SuperSU pro but it didn't work. I tried KingRoot and TunesGo, with no result. I am not sure why the Magisk or SuperSU is not working? I don't know what else to do, I would very much appreciate help. Thanks!
[Magisk] jcmm11:
https://xdaforums.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
[Magisk] martyfender:
I hope you didn't use my exact command, unless, of course, your twrp image is actually named "twrp.img". You substitute the actual name of your image in that command. I put the twrp image in my adb folder on the PC, if using Windows, then shift, right click on an empty space in that folder: "open a command prompt here"

On Linux Mint I only have to to do that in what ever folder I have it in.

On Windows, you have to have the system wide environmental variable set for it work like this in Windows, I believe. Despite having that set in Windows, I still think it is easier if you just have the twrp image in the adb folder.

If you did choose the exact name of your twrp image in the fastboot command, and it failed, then I am not sure what is going on.

Here is what I get on Linux Mint:

mint@mint ~/Downloads $ sudo fastboot flash recovery twrp.img
error: cannot load 'twrp.img'
mint@mint ~/Downloads $ sudo fastboot flash recovery Ares8A_recovery_twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (12848 KB)...
OKAY [ 0.445s]
writing 'recovery'...
OKAY [ 11.739s]
finished. total time: 12.185s
mint@mint ~/Downloads $

Note: on Windows you do not use the sudo command.

Another thing you can try is to temp boot twrp:

fastboot boot recovery twrp.img

make sure you substitute the exact name of your twrp image in this command if it is not twrp.img

hit enter and if all is well it should boot directly into twrp. If it doesn't it may be the wrong twrp for your device or the image could be corrupted?

Maybe you can get help with it on your device forum, if twrp still fails.

Did you state what Android version you have? Also, if it is an A/B device, the procedure for flashing twrp will be different, as A/B devices don't have a separate recovery partition but have it in the boot.img, booted from the ramdisk.

UPDATE:

Here is one of many that I found for your device:

https://xdaforums.com/v20/development/recovery-twrp-3-1-0-0-touch-recovery-t3603760
[Magisk] Oery:
Magisk forced closed, when tap to LOG

Magisk v.18.0 (stable)

Magisk Manager v.6.1.0(165)

Redmi 4X (santoni)

On AOSPExtended v6.1 (Official)

(Android v9.0)

Note:

Back to Magisk v.17.3 (stable)

Magisk Manager v.6.0.1

Working, no FC
[Magisk] PistolSlap:
Hmm, thank you. I tried using the method "Root/Reroot with Magisk - Pass SafetyNet With patched_boot.img" and went through the process. When I rebooted the system it went to Android stock recovery with a message saying "Can't load android system. Your data may be corrupted." >.< I'll see if I can try another method.
[Magisk] AntholifeV2:
Hey; since I root my S9 with magisk. The secure startup option (a code is requested at startup to decrypt the device.) Out of this flash this option has disappeared Maybe because of dm-verity? I would like to find this option ..
[Magisk] 124112:
Thank you for replying. I copied and renamed it to the simplified version, not blindly pasting commands. I know slightly better than that!

I don't remember what Android version, and don't want to guess, as I don't remember updating to Pie. Most likely still on Oreo.

When I tried to temp-boot TWRP, I got this command:

fastboot: error: cannot load 'recovery': No such file or directory

edit: going to try using quotes and directory

edit2: Unsuccessful, even after putting twrp.img in the adb PATH directory.
[Magisk] jcmm11:
Are you sure you have the latest fastboot version?
[Magisk] chteh0721:
I'm using Mi A1, after recent update to Android 9 aka Pie, my magisk (v18) don't allow me add any modules, it only allow me to add 7 modules, any modules more than this it wont show out in the magisk manager. No error message been shown. May i know how to troubleshoot this ?
[Magisk] 124112:
Yes, 28.0.1, the latest version of adb and fastboot as of September.
[Magisk] Didgeridoohan:
Do you have TWRP installed? If so, make sure to restore the stock boot image and only

boot

TWRP if you need it.

Go the other direction: install Canary debug build and if the issue continues make sure to provide logs.

Provide logs...
[Magisk] TiZiO.Cover:
Just wondering, are there any reports that Hide Magisk fails on the OnePlus6 OB10?

Root and Magisk Hide are working fine though.

I tried 18 and the latest canary built.
[Magisk] simplepinoi177:
I believe you simply have the syntax wrong..... why is fastboot showing an error about you calling for a "'recovery: No such file or directory'"??? Like [MENTION=8126387]martyfender[/MENTION] said, A/B devices don't have a "recovery" partition anymore, the recovery is inside/part of the boot partition and image -- no longer it's own partition or place in the device. So, unless your TWRP image file is actually named "recovery.img", nowhere should you be inputting the word "recovery" (at least for A/B devices).

For my Pixel 2 XL, temp booting TWRP is inputted as follows:

fastboot boot "C:\Users\[name]\Desktop\platform-tools 28.0.1\twrp-3.2.1-2-taimen.img"

*keep special note that it is

not

input as "fastboot flash boot" -- for doing that will replace the regular normal boot partition with the TWRP custom recovery (only) image and bootloops abound.

I imagine the syntax should be the same for your device (it's pretty much standard fastboot commands and the way A/B devices are set up), but even if not, I'd hope you can figure out how to apply it to your device...

Good luck to you and hope this helps...

---------- Post added at 02:43 AM ---------- Previous post was at 02:32 AM ----------

Be sure you're not trying to "flash" the Magisk .zip installer or something (specifically using fastboot) as it's only meant to be installed by TWRP or like-custom-recovery. If anything, you should only be "flashing" (via fastboot) a Magisk patched boot image. It's kind of like this twitter post where people are flashing TWRP's actual image instead of just using the image to temporarily use TWRP so you can install it proper with TWRP .zip installer...

Hope this helps...
[Magisk] WizP:
Magishide wasn't working for me.

Just finished a little debugging on my Samsung N8. Banking apps would discover my device was rooted.

Turns out there is a 'su' link left in the '/sbin' directory on reboot... I just deleted the file, now everything seems to be working OK...

It's strange, as the apps were only detecting this intermittently... I.e. The problem would return after I accessed my banking app once.

So I guess the problem might come back, but maybe it helps with fixing some of the bugs
[Magisk] Homeboy76:
Do #4, then do # 8 don't use patched boot.img (#9).
[Magisk] Didgeridoohan:
Of course there's a su symlink to the Magisk binary. Hard to call su otherwise... But, when MagiskHide is working as it should the entire /sbin directory is unmounted so that it isn't detectable.

There is a known issue where MagiskHide isn't working reliably on all devices/setups. Noone's been able to provide much info for troubleshooting it though. See my posts on the subject from a little less then a day ago for more details.
[Magisk] gravityz3r0:
Ever since i upgraded to 18.0 from 17.3, my SafetyNet check (ctsProfile and basicIntegrity) has been failing randomly after an undetermined time. The only way to fix this is to reboot my phone, after which it will return again after some time. I can't seems to produce this reliably as it it has lasted anywhere between one week and 10 minutes after each reboot.

Is this a known issue? Thanks!

On a Samsung S7 stock ROM Android 8.0
[Magisk] qwer222:
Thanks for the info and guide. The latest official android OS for my phone is Android 5.0 (well you know the damn samsung not taking care their old flagship model once their new flagship launch), I never try the other custom ROM although it release by other developer.

I do tried TWRP to flash magisk before this, but it will take more time and effort than using magisk manager to patch boot.img and complete root in less than three minutes. Because I need to root the phone and unroot it back frequently, due to some app can detect magisk root and magisk hide not working on my phone old kernel.

Anyway I successfully install the old magisk with old magisk manager by change the update channel to custom address provided by good helper, which still link to official magisk download channel.
[Magisk] ktmom:
I'm curious, did you read any post in this thread, before you posted? Even just the two or three before your's.

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

May I ask, on such an old device, why not have stayed on a Magisk version that was developed back when it's OS was dominant? So much of the current development is to deal with issues created by the newer OS releases and A/B slot devices.

Just thinking, if it's not broken, don't fix it.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Magisk] Airpil:
Hi all is it possible to inject *.rc scripts with magisk ? I need to modify usb port behaviour based on the property change. I know i can simply replace one of the original init scripts, but i would like to keep my system in the original state.
[Magisk] martyfender:
Does

fastboot devices

return your device fastboot serial number?

Also I was trying to determine if you have an A/B device.

I found this guide for the lg-v20-h918:

https://xdaforums.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258

LG v20 xda forums:

https://xdaforums.com/v20

The newest twrp I found for your device:

https://xdaforums.com/v20/development/recovery-twrp-3-2-1-0-t3720239

I think you should get help in those forums.
[Magisk] guest4711:
I'm using the actual Magisk (unofficial builds) on all devices where it is supported (Galaxy Nexus {Maguro}, S4 {jflte}, Tab 2 {espressowifi} to be able to use actual modules without need to repack them with older templates.

And I think it would be good to check whether newer commits don't break functionality needed for older devices...
[Magisk] hofi01:
hy

I dont know, is it a Magisk or TWRP problem?

but...

in MIMIX2SGlobal_8.12.27 DEV TWRP v14 and China TWRP works.

but Magisk v18 give no root to the system =???

Please help?

greets
[Magisk] RandomPooka:
Have you installed the Magisk manager app? Or, did you only install the zip file?
[Magisk] hofi01:
i only intstall

Magisk-v18.0.zip

and magisk manager 6.1.0 is also installed before.

in this i have a short message...

Database for SU defect, it will create a new one.

but nothing changes

in TWRP all working fine... i can update my System Host file without problem....
[Magisk] guest4711:
Deinstall your current MM and install the one contained in the zip (folder common).

If this doesn't help flash the Magisk Uninstaller and Magisk afterwards.
[Magisk] fightinfilipino:
to be clear are you deleting the "su" file in the sbin folder in root?
[Magisk] hofi01:
hy

thanks for the info, after reinstalling second time MM, root is working again...
[Magisk] peterlee928:
hello all. i am unable to install the snet.apk from the canary release files. when i try to install via adb, i get the following message:

failed to install snet.apk: Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES: Package /data/app/vmdl1441952462.tmp/base.apk has no certificates at entry AndroidManifest.xml]

any thoughts on what the issue is and how i might be able to solve it?

much thanks in advance :)
[Magisk] jcmm11:
What, exactly, are you trying to install and how are you installing it? You shouldn't need to install anything via adb in order to install Magisk.
[Magisk] 124112:
I did use lafsploit to root my phone. I do not want to wipe the device right now, in case I am able to get into TWRP somehow and backup any data that may be left.

The reason I posted in this thread is that the incompatible Magisk update caused this, and was hoping someone with a similar experience had a solution.

As of now, I just have no idea why I can't boot or flash TWRP.

However, I will move this discussion out of this thread. Thank you for trying. May just have to accept my mistake, wipe data, and start over.
[Magisk] peterlee928:
i am trying to install the "snet.apk" file. it is one of the files that are in the canary release version file list on github.

EDIT

i already have the latest release version of canary installed.
[Magisk] martyfender:
Have you tried to flash your stock boot.img in fastboot to see if you get an error from it also?
[Magisk] guest4711:
Glad to hear ;)
[Magisk] Didgeridoohan:
The snet.apk is used by the Manager to check SafetyNet. That's the additional files that need to be installed the first time you check SN, you don't need to do anything with it...
[Magisk] jenslody:
You should not install anything from somewhere you don't know what it is for.

Snet.apk is an internal app needed by MagiskManager to check safetynet.

It's not directly included in MagiskManager because it contains non opensource parts.

It is not meant to be installed directly by the user.

Edit:

Ninja'd by [MENTION=4667597]Didgeridoohan[/MENTION] (again).
[Magisk] ktmom:
I'm not sure I can agree with this philosophy. The variety of current devices out there is daunting to support. To expect backwards compatibility for devices no longer supported by official releases makes development an overwhelming task. Just dealing with out of date kernels is problematic.

Modules being updated and breaking backwards compatibility is a real issue. I don't use modules, other than systemless hosts now, and I didn't realize there isn't a repo dependant on the version you are running.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Magisk] Strephon Alkhalikoi:
You mean Android version here, right? Magisk modules do have version control through updates to the module template, but that version control is tied to a version of Magisk rather than Android.
[Magisk] ktmom:
No, I guess I misunderstood what [MENTION=8010004]guest4711[/MENTION] was saying in his post.

If the modules are tied to a Magisk version, then I absolutely believe that there is a point at which users must understand that an update of Magisk is likely to break on an older device IMHO, it's unreasonable to expect compatibility across devices or officially unsupported Android versions.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Magisk] thorin0815:
Mi A2 Lite / Pie / 10.0.2.0 firmware / MM 6.10 / Magisk 18.0

Since I'm using Pie, I'm no longer able to uninstall or deactivate any installed module inside the manager. Manager says that the module will be uninstalled after the reboot, but nothing happens.
[Magisk] nfsmw_gr:
Searched the thread but I couldn't find any answer.

When I press on a module on the download page manager crashes on me and I can't read the description.

Anyone has a solution for that maybe?

Thanks.
[Magisk] RandomPooka:
Try going into the settings in the app and selecting "Clear Repo Cache"
[Magisk] ahamling27:
OnePlus 6 user here. Just updated to OxygenOS 9.0.3 and Magisk bootloops(boots to OS where it immediately shuts down) installing in TWRP. I can't even install in the Magisk app, just says 'Unable to unpack boot image, Installation failed'. I've uploaded the log too. Not sure what OOS changed from 9.0.2 to 9.0.3 but it's big enough to break installation. Any tips appreciated. Thanks!