yashsingh1/xdaforums huggingface dataset:
[Magisk] Lordsinko:
What about using another custom kernel like phantom kernel or something
[Magisk] ChrisFeiveel84:
Use the current Magisk beta (code1307) on my ZTE Axon 7 with Stock Rom 7.1.1

And have not had any problems so far
[Magisk] grego3140:
Inever Used another Kernel other than the Lss, I don't Know the more stable, you think with another Kernel the Magisk work ?
[Magisk] Lordsinko:
Yeh magisk for some reason didnt work with my kernel so i changed to arter i unistalled su and busy box in twrp then flashed magisk and thought i lost root aswell but after a minute i got 5 green ticks for it worked :) tried numerous kernels and only had it wirk for me on one kernel so far
[Magisk] grego3140:
Okay I'm going to tried a custom kernel Thanks :)
[Magisk] Lordsinko:
Let me know how u go also make backups my friend
[Magisk] als123:
exactly my case in redmi note 3 pro
[Magisk] xsteven77x:
Working great htc one M83 latest lineageos nighties. Does NOT and has not worked for awhile when put into core only mode. No biggie just putting it out there :)
[Magisk] king200:
Galaxy S7 G930F, SuperMan-Rom V2.5.0

Used Unroot SuperSu 279, restored boot.img, and flashed current version v13.0. Passed SafetyNet and "Google Pay" worked.

Problem, I could not write to MicroSdCard. Used Root Explorer and ES File Explorer. Each could not get permission to access the card to write or delete files. Is a module necessary? I don't know where to look.

Would like module to bypass necessity to have a secure lockscreen with "Google Pay".
[Magisk] bluenote73:
Last 3 betas are not working for me, although a previous one did. (Well previous 2 worked when flashed over top of previous install, but all 3 fail for root use right now on a virgin install).

What model are you? I'm on A2017U.

What is code1307? Can you detail which beta you are on?
[Magisk] brandonsisco:
Please help

I get same error after starting from scratch

E( 453: 503) mount /dev/block/loop0->/magisk failed with 13: Permission denied

Safetynet check fails, using latest Magisk v13 54e6a79

Motorola G5 Plus stock firmware 7.0 NPN25.137-33

Please advise
[Magisk] dkionline:
magisk image mount failed with error1 in twrp.

54e6a79

build 96f8efc working normal.

I use a Huawei P9 EVA-L09
[Magisk] mbl007:
Hey everyone, i have a op3t running latest open beta with twrp and super su. Can someone guide me on how to switch to magisk without losing anything? Can i just flash it in recovery over supersu? Any help would be appreciated.
[Magisk] TarikVaineTree:
Did you do anything special or did it work out of the box?

I want v13 on my S8 Plus as well because of some great new features. :)
[Magisk] loner.:
Works great on my HTC U11.
[Magisk] shadavis08:
Do I need to uninstall the old Magisk build before I install the new one or can I dirty flash over the old build? They are both beta 13 so I figured I'd ask.
[Magisk] tpuserhp:
Magisk manager stops if i tab on checking safety net status area. LineageOS 14.1 ROM for the OnePlus One Magisk v13.0 (54e6a79).
[Magisk] Iradj:
Yes you can flash it dirty, i did that too. No probs
[Magisk] blueoval50:
Dirty flashed successfully on my Nexus 6 running Pure Nexus rom.
[Magisk] Papabendi:
Nothing special at all. Had previously installed TWRP and v12 Magisk. I removed the old Magisk and restored my original boot image and then flashed v13 from TWRP and all worked fine.

I am using an international S8 as I'm from New Zealand.
[Magisk] Nodens:
Regressions happen in development. :) Try the zip I'm attaching on this post to see if it fixes it. If not I have another fix in mind.

I didn't see the error on your working installation log. dd clearly says it's failing to write a block and since it's the boot image we're talking about it can't be good :P

This is probably a side-effect though and not the cause of the issue.

The one in /system/bin is the rom default. The one in /sbin should be TWRP's. It's apparent that topjohnwu doesn't want to use TWRP binaries. He must have his reasons.

Just to indulge a theory can you also try the zip attached here and see if it works for you or not?

EDIT: Replaced zip with adding to library path possible fix.
[Magisk] atarek:
I installed v12 again to check magisk manager log is working or not and result was it's working flawlessly and log in manager logging tab. I returned to v13 and same behavior as quoted post "log is empty".

Any advise.
[Magisk] AndroidON:
Don't know why, but Magisk v13 is conflicting with Moon reader app.

Moon reader app works well with v12, but it just freezes when I install v13. (54e6a79)

Was on Galaxy note 3, 6.0.1 Marshmellow touchwiz.

Would you please fix it? Thanks. :D
[Magisk] dahawthorne:
Nothing to fix, as far as I can see. Moonreader Pro works perfectly for me.

Nexus 6, Pure Nexus, Magisk Beta 13 54e6a79.
[Magisk] AndroidON:
Well, you are on pure AOSP based rom and I'm on Samsung touchwiz rom.

As topjohnwu said on OP, magisk can behave different and I'm reporting that different behavior.

I don't know what is wrong, but Moon reader was clearly worked on v12 but not on v13.
[Magisk] jenslody:
No it does not work.

Your change just added the wipe-out of LD_LIBRARY_PATH content another time, this is already done in recovery_actions.

I guess the "out of memory issue" is misleading, because the script cat's the new image and /dev/zero and pipes it to dd with a blocksize of 4096. I think it's done to fille the rest of the device with zeros and without the count parameter it dd's from /dev/zero until the device runs out of memory.

So it's guaranteed that nothing is left from older images.

Not using TWRP /sbin is definitely not working on my J5. For whatever reasons some of the toybox binaries in /system/bin simply do not work (or need other parameters, because it's 1.22 and not 1.26, which is actual busybox).
[Magisk] Ortem1UP:
All good here

No problems to report. Working great on the LG MS210 or LG Aristo or LV3

Root successful, Install successful, Manager working and Safety Net Pass. Will test out modules next but so far so good.
[Magisk] KetoSoi:
Ran into a nearly identical issue on a 'project' I was involved in earlier this year. Google was looking for a specific package name, which we changed, and Google figured it out, and followed suit. Rinse, repeat.

In the end, we devised a relatively simple mechanism that allowed the end-user to specify a package name via a props file during install :) As the user could name it almost anything, each install was 'unique' in package name.

Youre right, it is cat-and-mouse... changing the color of the mouse only goes so far.

So, give them thousands of mice to chase instead :)
[Magisk] DodoGTA:
:laugh:
[Magisk] Nodens:
You are right. I missed the LD_LIBRARY_PATH clearing got moved in recovery_actions (actually I didn't check heh), I just assumed the missing clearing of the library path is what caused vitekrus777 issue of not finding the library. I guess the proper way would be to add /system/vendor/lib64 to the existing library path instead. Anyway since that was missing and we had one verified case of library dep issue I thought it may actually be related to your case as well (TWRP overriding some library). This means that in your case the system binary simply doesn't work (rom issue). And it looks like topjohnwu wants to entirely avoid using TWRP or busybox binaries. This means that all this functionality will have to be ported from script to code so that it works for every possible rom but for now your fix works. I will add it to the tracker. :)

Regarding the block write error you are also correct, I see it is cat concatenating image with /dev/zero to the dd pipe so it's definitely done to overwrite the rest of the space with zeros. And it's most likely that dd behavior (attempting to write the extra block and failing with error message vs not) may also be related to toolbox vs busybox :)

EDIT: Also edited the zip in the previous post with adding /system/vendor/lib64 to the library path instead for [MENTION=4166293]vitekrus777[/MENTION]
[Magisk] mbl007:
Anyone????
[Magisk] Bat-Maniac:
I don't know if it is usefull... but sometimes my mobile banking app crashes... sometimes it works fine...

I'm using Android O DP3 with elementalx 5.0 and latest magisk 13.0 on my Nexus 6P.

My mobile banking app is checked in magisk hide... Systemless adblocking is deactivated.

SafetyNet test is always succsessfull.
[Magisk] demonoidmaster:
Remove SuperSU and flash magisk -_-

PS: read the op, you can't flash Magisk over any other user installed or preinstalled root tools, remove SuperSU with it's dedicated uninstaller then flash Magisk.

---------- Post added at 10:44 AM ---------- Previous post was at 10:37 AM ----------

Word of advice, don't use Stericson, use Busybox by jrummy

Current Busybox version is 1.26.2
[Magisk] bluesky1126:
Well, though I don't have any chance to use stericson's now. I'd still like to know your reason why not to use stericson,

and why you recommend jrummy's busybox.
[Magisk] DEVILOPS 007:
What's wrong with stericsons busybox? I use the one by osmosis.
[Magisk] shadavis08:
I couldn't use his BusyBox if I wanted to it won't install on my phone ?
[Magisk] veez21:
Who's? osm0sis'?
[Magisk] shadavis08:
Stericsons . I just loaded jrummy and it installed fine. I wanted to install a mod last week but it required stericsons BusyBox but I couldn't get it to install for anything .
[Magisk] Paschfire:
A XDA Recognized Developer / Recognize Contributer, here is his main Odds & End Thread.

https://xdaforums.com/showthread.php?t=2239421&page=127
[Magisk] veez21:
Nah, it doesn't necessarily require stericson's. Try osm0sis' (linked by [MENTION=5866088]Paschfire[/MENTION])

---------- Post added at 11:27 AM ---------- Previous post was at 11:26 AM ----------

Lol, no. You misunderstood the phrase ?
[Magisk] Paschfire:
:p:D
[Magisk] vitekrus777:
Many thanks, the archive was installed in the recovery, but in the log many warnings from linker.

The log is attached.
[Magisk] Shubham_007:
Google updated safetynet again, we are waiting for new magisk built [MENTION=4470081]topjohnwu[/MENTION]

Thanks in advance
[Magisk] Lordsinko:
Magisk 13 running on my device with latest beta

And all of it passed approval was

SamsungGalaxy S6 sm-g920I

Thanks :)
[Magisk] apophis9283:
I've rebooted times and still pass safety net. Really the way you make that sound is so, "privileged". Thanks in advance does not excuse this nasty behavior that has plagued XDA. If it has been updated I'm sure when he has time, he will release an update. So be patient... Thanks in advance
[Magisk] Shubham_007:
Thanks passed successfully after reboot
[Magisk] Nulltown:
I'm suddenly failing SafetyNet with and without Core Only.
[Magisk] Shubham_007:
Try rebooting, it worked for me
[Magisk] Nulltown:
Tried it a few times to no avail.
[Magisk] bluesky1126:
Have you flashed any zip file or have done any things as root privilege after the last "SafetyNet Passes" check?
[Magisk] Nulltown:
I'm currently setting up a rom, so definitely. I'll try reflashing Magisk.

EDIT: Still fails.
[Magisk] tyler19820201:
Thanks for the Mv.13.

Great job.:good:

I have just installed now for OP3T with multirom and giving safetynet passed and the root also ok. However the automagisk app does not work...Do i have to update that one also?

I did not update SU phh and is outdated, however with Mv.12 the AutoMagisk was working fine weather i was updating or not the SU...

:confused:
[Magisk] Kiid:
Go to a terminal emulator

Enter "Su"

Then "magiskhide --enable"

Then run the SafetyNet check again
[Magisk] bluesky1126:
Which rom do you use? stock or custom os?

And you said that it "suddenly failed" , so has your phone ever passed SafetyNet in this rom before?
[Magisk] Nulltown:
OK, now it's passing again. Ignore me. I obviously don't know what I'm doing. :silly:
[Magisk] TarikVaineTree:
It's running great so far on my S8+ so thanks for your help. :)

However I definitely need Busybox for apps like DataSync but it won't install. How can I install Busybox?
[Magisk] jonnie77:
Works in note 4(n910f) flawlessly after flashing busybox racerom v11 with ramkernel rc4?????
[Magisk] bluesky1126:
https://xdaforums.com/showthread.php?t=2239421

Try this. It's systemless and works as a module in Magisk, which works perfectly with Magisk Hide on mine and many others' phones!
[Magisk] jukyO:
Maybe I fail to see it, but does v13 installs magisksu binary?
[Magisk] kgr:
Stericson BusyBox seems to break SN.

Osm0sis BusyBox seems to be systemless? Also it acts like a Magisk module.

For ages, all I ever used is Chainfires SuperSU & Stericsons BusyBox - first thing I ever installed lol. Now that I might care about passing SN, Magisk & Osm0sis BusyBox are working better.

try this...

*edit - what [MENTION=7905927]bluesky1126[/MENTION] said :)
[Magisk] TarikVaineTree:
Ok there is a UPDATE-Busybox.Install.zip to download.

Should I flash that with TWRP or install it as a module from within Magisk Manager? :)
[Magisk] kgr:
Yep, flash that from TWRP.
[Magisk] bluesky1126:
I flashed it through TWRP, but I think it's up to you.
[Magisk] Didgeridoohan:
It's an all-in-one installer. It'll adapt based on what you have installed. So: flash in TWRP.
[Magisk] otonieru:
Last time i flash 0smosis one, it's TWRP,

But you can try it on manager as well, since it will tell u anyway if its not compatible, :) in that case, simply flash it from TWRP
[Magisk] Skittles9823:
Magisk is it's own SU remove PHH's SU and then uninstall magisk (or flash your original boot image) and flash magisk again.
[Magisk] Viggen66:
Whenever I install Magisk on an Android TV, it boots fine, but on reboot, it appear "Apps are optimizing", well this didn't happen on supersu, but I have looked on the rom itself, it has the framework/arm folder, meaning apps are not optimized on dex file, I wonder if I install Magisk after first boot, this bug disappears on magisk?

When I looked on google knowing the reason why it happens I looked at this

"Why Optmizing app happens?

1- During boot app apk files are converted into somekind of 'optimized' dex file.

2- These files are stored under /data/dalvik-cache/arm/

3- During Reboot somehow those dalvik-cache files vanished or probably /data/dalvik-cache/arm files will be removed when system needs more space.(directory-name itself says its cache, so its not a surprise, anyway).

4- Now step 1 gets repeated for all apk files in the mobile."
[Magisk] TarikVaineTree:
Thank you guys. Flashing Busybox.zip through TWRP has worked.

However the App DataSync won't sync anything but that might be an issue with the app (last update is from 2014).

Does anybody know a better app to sync app data via root over GDrive?
[Magisk] bluesky1126:
Take a look at the famous Titanium Backup?
[Magisk] Nodens:
Ignore those warnings. I'm not entirely sure why they are happening but I can tell you what they are.

When a path is expected to be found in a zip file normalize_path is called to normalize the entry name.

This is the relevant code snippet from android source:

if (!normalize_path(original_path, &normalized_path)) {
DL_WARN("Warning: unable to normalize \"%s\"", original_path);
continue;
}

Your errors show "", an empty original path not getting normalized. They are harmless, so if the workaround is working you're good to go until

there's an official solution :)
[Magisk] shadavis08:
Which version of BusyBox ?

If it's stericsons it wouldn't work on my phone either but jrummy's BusyBox worked like a charm. Osmosis busybox is supposed to work fine too
[Magisk] bluenote73:
After flashing stock system, and installing v13 54e6a79, root constantly crashes Magisk Manager. Could someone please read my logs and tell me if there's anything worthwhile there? I have cleared data of MM, reinstalled, etc.

I'm on an Axon 7 A2017U stock 7.1.1 Nougat.

I have uploaded my boot.img to topjohn's github.

(attached logs)

thanks
[Magisk] loner.:
Am I missing something? I can't get the Magisk version number to light up green.
[Magisk] moosefist:
This fixed the safetynet check for me. Thank you
[Magisk] adrenochrome25:
Xiaomi Redmi4X (santoni) / TWRP 3.0.3-0-609f78a3 / android 7.1.2 N2G47h / MIUI 8.6 by xiaomi.eu 7.6.22 beta

rootchecker (joeykrim) detects root despite being added in magiskhide settings, please find attached :

- resetprop_log.txt

- magisk_debug.log (external because too big for the forum)

magisk log of rootchecker try :

- magisk_error_20170630_220239.log

and just in case, installation logs :

- recovery.log

- dmesg.log

any idea of what's going wrong ? (v12 magiskhide was working perfectly)
[Magisk] demonoidmaster:
Because of that one time where Stericson pushed a bad version (broken) of Busybox to the playstore making multiple people have malfunctioning devices and such other things, that and the fact that he hadn't updated his app or the Busybox version in so long during the MM days of android

---------- Post added at 10:34 PM ---------- Previous post was at 10:32 PM ----------

Hence why i said don't even bother with Stericson's one, it's still pretty bad even today, that's the reason Jrummy updated his app, because of people having been stuck with a broken Busybox installer when Stericson had updated his app but still used an old version of Busybox in it along with the app screwing up Android installs

---------- Post added at 10:36 PM ---------- Previous post was at 10:34 PM ----------

Mine still says passing
[Magisk] brujo5:
Noxxx kernel dev for S6 :

Seems MAgisk v13 not working due updated ramdisk (june).. time for magisk to find a new workaround, because im not downgrading
[Magisk] Wolfcity:
Just my two cents, I'm using Meefiks busybox from playstore, it installs to xbin as it should (surely to other places too), I've got viper4arise working with it and pass safetynet check with magisk 12 plus fix module.
[Magisk] shadavis08:
I'm passing still with the newest update to the beta
[Magisk] shadavis08:
See !
[Magisk] heri1978:
Use ydf busybox, safetynetfix module, magisk v13. A few rebooted still bypass safetynet. Shared about this, on G+, but some guy told its not busybox related (yeah, most of my applets not symlinked, and you said it's not related). Ok,happy struggle.
[Magisk] TarikVaineTree:
Oh no I screwed it up somehow. :(

It was running so nice on my S8+ until I installed this module from within Magisk Manager's Download tab:

https://xdaforums.com/apps/magisk/magisk-unified-hosts-adblocker-t3559019

When the popup for the restart after the install came I proceeded to reboot and now it's showing me the Samsung logo for a few seconds, turns screen off, vibrates, shows the logo again for a second and automatically boots into TWRP. :(

Is there anything I can do to undo that module Installation from within TWRP or do I really have to wipe and set up my whole phone again?

I tried booting into system from TWRP but always the same result: a short "bootloop" that leads into TWRP.

Edit: I did a full backup now in TWRP so I can extract and use my savegames from /data just in case I really would have to do a wipe.

But I still hope I don't have to and there's a better/quicker solution.

In the modules thread I found this:

Can anyone tell me how to use this with TWRP to undo the install of the hosts adblock module that screwed my phone up? :)
[Magisk] loner.:
Ok I will ask again.

How do I get the Magisk version number to check green?
[Magisk] lucastracq:
ask it a third time. it will fix that.
[Magisk] Captain_Throwback:
Make your font/display size smaller.
[Magisk] drewski_1:
Human sacrifice. It worked for me (yeah, still v12)
[Magisk] rignfool:
Cool story bro...
[Magisk] loner.:
Thank you!

Eyesight is not what it used to be.
[Magisk] DeluxeMark:
Some of my apps doesnt open,i just reinstalled my magisk that was giving a safetynet error
[Magisk] kastik4:
in magisk 12 there was an option within the app to keep force encryption and dm verity how enable them in magisk 13? thres is still an option to do that but when i tap them and exit the app they stop being checked
[Magisk] TarikVaineTree:
Woohoo! Sorry for quoting myself but I thought this might be useful for anyone as I got it working again within seconds. =)

The steps:

Download "Magisk Mount" zip

boot phone into TWRP and connect it to PC

copy zip to internal storage

install/flash the zip

in TWRP main menu go to "Advance" and "File Manager"

click on /magisk, then on the folder name of the module that causes your crashes

click on the lower right folder icon and chose "delete"

optional: flash the zip again to shrink your img file

reboot to system
[Magisk] Borfas:
Hello, Any one explain what version apk and what zip is last version for galaxy s8 ? Thank you !
[Magisk] schmeggy929:
Um that would be the big orange colored link that says Download next to Release Note and Changelogs in OP.
[Magisk] ForgottenDude:
Flashing Magisk Uninstaller wouldn't have fixed it?
[Magisk] Borfas:
i ask and you what do you answer ?

is topic explain for SAMSUNG GALAXY S8 ? Write somewhere and i do not see ?
[Magisk] schmeggy929:
This is a Universal Systemless Interface Android 5.0+. Install and if you see any issues report them here, that's what this thread is for. That means try it on any Android 5.0+ system and report.
[Magisk] Spannaa:
Magisk isn't device specific ;)
[Magisk] dkionline:
But problems can be.
[Magisk] jenslody:
And that's what the Beta-thread is for:

test if there are any problems and report them here (with appropriate logs) if any.

But everybody is free to search the thread before trying it, but it also depends on the used rom, so the device might not be enough to search for.
[Magisk] NeoBeum:
While I was experimenting with FOTA Upgrade with the Z5 Compact, I found the Play Store and Service is currently hiding the app launch icon from home screen and apps setting when first installing Magisk Manager. I had to clear Dalvik after full uninstall to reinstall with SU and have App Icon visible
[Magisk] TiTajm:
Guys what do I do wrong? No safetynet pass, I got the latest xiaomi.eu. What is funny - AndroidPay works and everything but still it shows that something is wrong. Ofc i have installed module for gemini.
[Magisk] DodoGTA:
MIUI isn't compatible with Magisk Hide
[Magisk] ygb7:
How do I get Busybox installed & working with Magisk 13?

I TWRP flashed [BETA][2017.6.24] Magisk v13.0 (54e6a79). It installed fine. I pass root check.

My problem is installing busybox does not work. I tried Busybox (Stericson) & Busybox (JRummy). Both install without error. However, when test by typing awk in terminal command window it does not work. Apps also say no busybox installed.

Magisk 12 had option to enable use of busybox. I do not see that option in Magisk 13 Beta.
[Magisk] DodoGTA:
You can use [MENTION=4544860]osm0sis[/MENTION]' busybox (It supports Magisk, but it can't be flashed with Magisk Manager): https://xdaforums.com/attachment.php?attachmentid=4110436&d=1492031915
[Magisk] ygb7:
I solved the problem myself by TWRP flashing @YashdSaraf Busybox using link BusyBox 1.26.2 Flashable and BusyBox Cleaner (All Architectures)
[Magisk] grego3140:
Hello, I have a bad new.

With another kernel Magisk don't work...
[Magisk] muhammedali:
Hi am using magisk was working all fine now it states not rooted functionality greatly limited any fix please
[Magisk] daddylonglegs:
Is there any way with Magisk that I can edit the systemui.apk and push it back to the phone? If so, it would remove 95% of my need for Xposed/Gravitybox. :)
[Magisk] yochananmarqos:
1. Wrong place to ask, read the OP.

2. Don't cross-post.

3. You've already asked twice and received the answer twice.
[Magisk] guest4711:
Reboot your phone. If this does not solve the issue dirty flash msgisk.zip again via twrp.
[Magisk] muhammedali:
Ok many thanks for your fast response will try it
[Magisk] Lordsinko:
hey wat kernel u try also when u flashed the kernel did u flash un su and busy box unistaller than flash magisk

Can get files from below

unsu zip by osm0sis ( https://xdaforums.com/attachment.php?attachmentid=3931994&d=1478779893)

Busybox unistaller by Phil3759 ( https://xdaforums.com/galaxy-s2/themes-apps/busybox-uninstaller-v1-0-remove-busybox-t1853419 )