Database Develop

Magisk v14.0 - Root & Universal Systemless Interface For Zenfone 2 (Z00A/Z008)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Latest Stable Magisk Version : v14.0 [2017.9.6]
Latest Magisk Manager Version : v5.3.0 [2017.9.6]​
Hello, welcome to the official Magisk Release For Zenfone 2 Z00A/Z008 taken from 4pda.ru forum!
Magisk can ROOT your device, along with standard common patches.
It packs with a super powerful Universal Systemless Interface, allowing unlimited potential!
Magisk modifies boot image and add files to /data and /cache
It touches your /system partition only if root installed in /system is detected!
Features
100% fully open source and easy to build!
Magic Mount :
Allow you to do any system (vendor) modification without actually tampering the partitions.
Anything can be loaded with Magisk systemless-ly!
MagiskSU : Open Source Root Solution
Root your device with MagiskSU, based on phh's Superuser, which is based on CM Superuser.
Magisk Manager :
MagiskSU Root Management, Upgrade Magisk in-app,
Manage, Upgrade, Download, Install Magisk Modules from the community driven online Magisk Module Repo.
Magisk Hide :
Hide Magisk from detection, mainly targeting Google's SafetyNet
Resetprop :
Allow you to do any modifications to system props (build.prop), including read-only props.
It is also used along with magiskhide for tricking various device states
Multiple Entry Points :
Provide several entry points to developers, reliably pausing the boot process before everything is done.
Include post-fs (cache) mode, which happens even earlier than data is mounted (used to replace Boot Animation etc.)
Standard Stuffs :
Remove dm-verity, forceencrypt, unlock partitions blocks to support remount to rw
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager Through TWRP Recovery
For installing Magisk the first time!
(never update magisk through application it will caused bootloop)
(If you have Xposed safetynet won't work)
Install Lastest Magisk Manager Apk
Reboot To TWRP Recovery
Select Lastest Magisk ZIP, then flash it
Reboot To Systems (wipe cache and dalvik is'nt needed if you want it then go for it)
Downloads
Lastest Magisk : https://drive.google.com/file/d/0B_t_ymFu4cH4eDNaYkhjU3lJb28/view
Lastest Magisk Uninstaller : https://drive.google.com/file/d/0B_t_ymFu4cH4bktMb2xTdk10Yzg/view
Lastest Magisk Manager Apk : https://drive.google.com/file/d/0B_t_ymFu4cH4dkpNUHh3NXVuOWc/view
Credits & Specials Thanks To All Developer XDA Forum & 4PDA Forum!

where to get uninstaller?

Arerive said:
where to get uninstaller?
Click to expand...
Click to collapse
haha forget to add it, wait bro

nice, thanks you so much, btw i had Magisk 13.3 installed, do i need to remove my module before flashing the new Magisk?

sushuguru said:
nice, thanks you so much, btw i had Magisk 13.3 installed, do i need to remove my module before flashing the new Magisk?
Click to expand...
Click to collapse
no just reflashed is ok bro no problem, same source.
mine from 12.0 to 14.0 without anyproblem

FYI : if you have xposed installed, safetynet won't work or gone

Thanks for the update! just relating here a mess i did:
You noticed the update today 2:15am XDA time, so i did wrong, opened Magisk Manager, and did the update.
what do i did to fix it:
1 -Once having Viper OS 3.0 on pc, i downloaded magisk installer, plus last HoloN kernel i was using. Taking advantage of that I was doing a dirty flash, i also down'ed last Gapps (but down'ed wrong version . . .)
Turned off phone, toke SD & plug on PC, put all downloadeds in external SD card;
2 - My Z00AD was in bootlop, so i reboot it in recovery and:
3 - Advanced Wipe > Wipe DAlvik/art cache + System + cache (JUST IT ONES!);
4 - Install ROM > Install last HoloN 6s0 version > flash Gapps and ... I downloaded x86-x64 version. Stopped here. . .
. . . So i had a previous Gapps version on PC, then . . .
Turn off Phone > pull out SD card & place x86pico 7.1 gapps version on SD
reboot ZF2 in recovery > did all step by step again:
1 - Advanced Wipe > Wipe Dalvik/art cache + System + cache (JUST IT ONES!);
2 - Install ROM > Install last HoloN 6s0 version > flash Gapps > flash Magisk > reboot.
So, i hope no other ones pass thrught that, keep attention with root stuffs . . .

El Cruz said:
Thanks for the update! just relating here a mess i did:
You noticed the update today 2:15am XDA time, so i did wrong, opened Magisk Manager, and did the update.
what do i did to fix it:
1 -Once having Viper OS 3.0 on pc, i downloaded magisk installer, plus last HoloN kernel i was using. Taking advantage of that I was doing a dirty flash, i also down'ed last Gapps (but down'ed wrong version . . .)
Turned off phone, toke SD & plug on PC, put all downloadeds in external SD card;
2 - My Z00AD was in bootlop, so i reboot it in recovery and:
3 - Advanced Wipe > Wipe DAlvik/art cache + System + cache (JUST IT ONES!);
4 - Install ROM > Install last HoloN 6s0 version > flash Gapps and ... I downloaded x86-x64 version. Stopped here. . .
. . . So i had a previous Gapps version on PC, then . . .
Turn off Phone > pull out SD card & place x86pico 7.1 gapps version on SD
reboot ZF2 in recovery > did all step by step again:
1 - Advanced Wipe > Wipe Dalvik/art cache + System + cache (JUST IT ONES!);
2 - Install ROM > Install last HoloN 6s0 version > flash Gapps > flash Magisk > reboot.
So, i hope no other ones pass thrught that, keep attention with root stuffs . . .
Click to expand...
Click to collapse
as I said on the post, dont update magisk from apk stuff you will get bootloop hehe

I installed it and reboot but my phone stuck at the Oneplus - Powered by Android Logo. Can someone help me? Im using Oneplus 5 btw

Andy1N said:
I installed it and reboot but my phone stuck at the Oneplus - Powered by Android Logo. Can someone help me? Im using Oneplus 5 btw
Click to expand...
Click to collapse
Try flashing Uninstaller zip first, and then flash the proper magisk package for your mobile... If you look at the title, you will see here "... for Zenfone" [emoji52]
Inviato dal mio ASUS_Z00AD utilizzando Tapatalk

Andy1N said:
I installed it and reboot but my phone stuck at the Oneplus - Powered by Android Logo. Can someone help me? Im using Oneplus 5 btw
Click to expand...
Click to collapse
bro its for zenfone 2 hahaha ??

Does it work with BORETS rom? And can i just flash it via recovery with borets rom?

@indunrise bro., i think the zip missing a file when installed.,the "busybox" file should be in /data/magisk/ since the newest magisk module uses that file to run.,but its absent.,so im keep getting error 1 when flashing any new v14.0 modules through twrp...it works fine now after i've put the "busybox" file at the proper place i've mentioned above...can u include the busybox file into the zip n give it proper permission ? Thanks

Here u go @indunrise

sushuguru said:
Does it work with BORETS rom? And can i just flash it via recovery with borets rom?
Click to expand...
Click to collapse
yes you can, im using borets roms

Luq4dmin said:
@indunrise bro., i think the zip missing a file when installed.,the "busybox" file should be in /data/magisk/ since the newest magisk module uses that file to run.,but its absent.,so im keep getting error 1 when flashing any new v14.0 modules through twrp...it works fine now after i've put the "busybox" file at the proper place i've mentioned above...can u include the busybox file into the zip n give it proper permission ? Thanks
Click to expand...
Click to collapse
thanks for report bugs, if i have some time will add it soon

Luq4dmin said:
Here u go @indunrise
Click to expand...
Click to collapse
if you guys needed module on magisk download and copy this to data/magisk

I've installed this, root working and satefynet passing. How can install xposed now? I've tried with app and xposed-v87.3-sdk23-topjohnwu.zip file, neither worked.

I flash magisk on lineageos and success, work fine.
But then I switch to XOSP rom of nilac and can't flash magisk. I did the same steps.
Do you know how to make it work? Thanks in advance @indunrise

ketrooo said:
I've installed this, root working and satefynet passing. How can install xposed now? I've tried with app and xposed-v87.3-sdk23-topjohnwu.zip file, neither worked.
Click to expand...
Click to collapse
Which version of Android are you using
Sent from my Z00A using XDA Labs

TWRP 3.2.0.0 Moto Z2 force [Nash]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All seems to be working except Encryption.
So that means you have to erase usedata!
If you don't know how to return back to a working state if something is broken, please think twice before flashing this.
Please do read the installation guide note !
IMPORTANT NOTE :
Warning: Make sure you make a backup of all your important data manually before flashing anything, making any backups or restoring.
I'm not responsible for any data loss, bricks, or whatever went wrong on your device. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
If you plan on using this on stock and have no root you wont be able to see any files due to encryption. To fix this FORMAT not wipe userdata then either flash supersu and not pass safety net or flash one of my roms(New one incoming)
Working
Everything except what's not working, see below
Not working / issues
Encryption
Logs
To get logs: Advanced ---> Copy log
Installation Guide :
1. Download all files below on pc.
2. BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
2.5 BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
3. Boot your phone to fastboot mode.
3.a If you already have twrp disregard the next 2 lines
4. Flash the twrp from below. Using the command "fastboot flash boot /path/to/twrp.img
5. Boot to recovery through the fastboot menu.
6. Go to wipe---Format data(FOR UNENCRYPTION)
6.a IF ALREADY UNENCRYPTED JUST MAKE SURE YOU REFLASH YOUR ROOT OPTION
7. When it says type in yes do it.
8. Wait to finish then plug phone into pc.
9. Transfer supersu to your phone.
9.a Transfer magisk if you use it
10. go to install and find the supersu/magisk zip you just pulled over.
11. Flash it and reboot.
12. Profit!
12.25 Go through the setup process to get to settings. Go to security and check it your phone says encrypt. If it does your good.
IF WANTING UNENCRYPTION ON STOCK YOU HAVE TO FLASH SUPERSU AS MAGISK DOESNT FULLY UNENCRYPT THINGS YET IF ON A ROM LIKE MINE FLASH WHAT EVER LOL
Update Guide:
1. Download new twrp
2. Boot to twrp
3. click on downloaded twrp
4. flash
5. REFLASH WHATEVER ROOT YOU HAD SUPERSU OR WHATEVER OR ELSE YOU WILL BOOT LOOP!
Download Links :
Newest TWRP FLASHABLE PLEASE TAKE A LOOK AT NUMBER 5 ABOVE
FASTBOOT FLASHABLE TWRP 3.2.0.0
Newest SuperSu
Newest Magisk
CHANGELOG:
V3.2
UPGRADED TO LATEST 3.2.0.0
ADDED LATEST UPSTREAM FROM @Uzephi
V3.1
FIXED BOOTLOOP
NEWEST KERNEL AT THIS TIME OF WRITING
V3
Ability to flash bootlogos!
Ability to backup and restore bootlogos
Ability to Backup,Restore and wipe OEM partition.
Ability to flash magisk(must be stock with oem partition in tact to PASS if your ok with cts profile mismatch then modify all you want)(Our phones use the new AVB Verity DM Verity 2.0 pretty much lol)
Bug Fixes and other stuff im forgeting.
Twrp is now flashable! just download the zip in the current twrp and flash!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:JBATS
Source:JOEMOSSJR
Kernel Source:JOEMOSSJR
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-11-10

Nice
Sent from my SM-N930F using XDA-Developers Legacy app

Woow, very nice present GREAT JOB!!!

Great job man. The people in our group can't thank you or your people enough. We appreciate all the hard work you guys did to get this working for us. Thank you again!

In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.

Uzephi said:
In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.
Click to expand...
Click to collapse
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.

jbats said:
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.
Click to expand...
Click to collapse
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.

Uzephi said:
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.
Click to expand...
Click to collapse
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:

jbats said:
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:
Click to expand...
Click to collapse
My kernel source can be built after a clone with any Linux install. I was actually going to upstream it this weekend, so no kernel work was needed besides the upstream.

joemossjr said:
All seems to be working except Encryption.
So that means you have to erase usedata!
Please do read the installation guide note !
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
Installation Guide :
Make sure you have unlocked bootloader
Backup all the data because it will be formatted
Reboot to bootloader
Use the command fastboot erase userdata
fastboot flash boot TWRP3.1.1.0nash.img (if you want permanent flash) or fastboot boot TWRP3.1.1.0nash.img (if you want temporary boot)
Then use @Chainfire cfar we have and run it normally (if you need instructions there here)
Once this does its thing you will have root and twrp!
boot to system and go through the setup process and make it to settings ----> security and see if you see encrypt.
If you do that means your good! You can now reboot to recovery and do what you want!
Download Links :
TWRP 3.1.1-0
CFAR
Bugs: Right now if you flash magisk it wont boot up due to the kernel not being decryptable still working on it atm!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:https://github.com/jbats/android_device_motorola_nash-twrp
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-10-11
Click to expand...
Click to collapse
(instructions were not clear I got my **** stuck in the toaster) jk but could I still do it if I didn't use cfar and got SuperSU a alternate way or will it not affect it

Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good

joemossjr said:
Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good
Click to expand...
Click to collapse
Another question would I be able to flash this with flashfire my computer isn't booting up and if yes what would I select? (And yes I'm very new to all this I only started last year with all this Android modifications)

How are you rooted

joemossjr said:
How are you rooted
Click to expand...
Click to collapse
I'm on the stock boot image with SuperSU installed just a normal root no Xposed and no magisk either although I had magisk originally
( I used a friend's computer when I went to visit him if that's what you meant)

thread updated if any questions please pm me

Thanks ..getting device tomorrow ....
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
Thanks ..getting device tomorrow ....
Click to expand...
Click to collapse
No problem!

Is this all I need to do to get root and twrp?/seems simple or to simple to be honest.I know nothing about how to root/ROM a motoz..Had a z droid but was verizion..Got a tmo zforce2 coming ..
Sent from my Nexus 6 using Tapatalk

Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?

Amd4life said:
Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?
Click to expand...
Click to collapse
your files are all jumbled because you didnt format data. xposed wont write right for some reason idk about the sound mod tho. Im about to update twrp here shortly

[GUIDE] How to Uninstall a Magisk Module (bootloop fix)

For those who encounter a bootloop because of a Magisk Module or got a bootloop during an update because of a module
This will allow you to go and delete that bad module and allowing you to boot back into the OS
What you need:
Recommended TWRP from TWRP 3.3.1-xx Unified Unofficial by mauronofrio
**Official TWRP may not allow you to boot twrp.img**
OOSNativeCallRecording Module seems to be one culprit. Make sure to Uninstall before updating.
If you already have twrp then go to Instructions
If you do not have TWRP and do not want to Install, use this method
Boot to TWRP (for those of us who do not install TWRP)
Does not work with OxygenOS 9.5.3 and below
Make sure to have adb and fastboot files here
1. Download the TWRP image (not Installer) from post above
2. Boot to fastboot
3. Rename TWRP image to twrp.img and move to folder with adb and fastboot files (after you had extracted)
4. Type
Code:
fastboot boot twrp.img
Instructions
1. Boot to TWRP
2. Go to Advanced > File Manager > data > adb > modules
3. click on the folder of the module you want to delete
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. while inside that folder click on the little folder on the bottom right with the check mark on it
5. click Delete
Done... Reboot back to OS without a bootloop

you should add what to do if you can't boot twrp. Happened to me after I removed Google dialer framework. Only thing I could get it to is bootloader. would not let me fastboot TWRp. I got an error every time. I had the flash boot image

mac796 said:
you should add what to do if you can't boot twrp. Happened to me after I removed Google dialer framework. Only thing I could get it to is bootloader. would not let me fastboot TWRp. I got an error every time. I had the flash boot image
Click to expand...
Click to collapse
This happened to me the other day. Took me an hour to figure out that all I had to do was fastboot boot.img.

diaztradeinc said:
This happened to me the other day. Took me an hour to figure out that all I had to do was fastboot boot.img.
Click to expand...
Click to collapse
I will update it shortly, thank you for the feedback.

Bradl79 said:
For those who encounter a bootloop because of a Magisk Module or got a bootloop during an update because of a module
This will allow you to go and delete that bad module and allowing you to boot back into the OS
What you need:
TWRP from here
If you already have twrp then go to Instructions
If you do not have TWRP and do not want to Install, use this method
Boot to TWRP (for those of us who do not install TWRP)
Does not work with OxygenOS 9.5.3 and below
Make sure to have adb and fastboot files here
1. Download the TWRP image (not Installer) from post above
2. Boot to fastboot
3. Rename TWRP image to twrp.img and move to folder with adb and fastboot files (after you had extracted)
4. Type
Code:
fastboot boot twrp.img
Instructions
1. Boot to TWRP
2. Go to Advanced > File Manager > data > adb > modules
3. click on the folder of the module you want to delete
4. while inside that folder click on the little folder on the bottom right with the check mark on it
5. click Delete
Done... Reboot back to OS without a bootloop
Click to expand...
Click to collapse
Just install the magisk module "Magisk Manger for Recovery".... Done. No need for such long instructions...

matze19999 said:
Just install the magisk module "Magisk Manger for Recovery".... Done. No need for such long instructions...
Click to expand...
Click to collapse
It's actually pretty simple, u just have to provide more instructions for people who haven't used twrp. There is no need to flash anything, ik that the uninmod does not work and I thought I tired mm and could not get it working either.

I use MM for TWRP since years and it always worked perfectly.

matze19999 said:
I use MM for TWRP since years and it always worked perfectly.
Click to expand...
Click to collapse
Have u used it with ur 7Pro yet? I tried it yesterday and would not flash along with uninmod would not mount magisk, I think it's issues with dual partition bc it did the same with my OP6

Bradl79 said:
Have u used it with ur 7Pro yet?
Click to expand...
Click to collapse
yeah. Whats not working for you?

matze19999 said:
yeah. Whats not working for you?
Click to expand...
Click to collapse
Got error when flashing, would u mind sharing the file?

Bradl79 said:
Got error when flashing, would u mind sharing the file?
Click to expand...
Click to collapse
I got the one to install from the download section but I've never used it I'm not sure how it works

He's right uninmod and stuff like that doesn't work at all now. It's unable to mount magisk.img it seems to be an issue with our twrp.
As for the statement about the issue being dual partitions that's wrong it's has nothing to do with that. I know he mentioned that uninmod and others did not work on op6 as well.. But it did cause I used uninmod on my 6 and 6T. This is an issue with this device only and possibly the twrp we have currently.

You saved my ass today! I updated to 9.5.9 and had bootloops. I forgot to disable my magisk modules :silly:

equlizer said:
You saved my ass today! I updated to 9.5.9 and had bootloops. I forgot to disable my magisk modules :silly:
Click to expand...
Click to collapse
Are u using OOSNativeCallRecorder module?

Yes i was using it. Just re-installed it.

Saved my ass!
---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------
So do we need to disable modules before updating? The re enable after?

spart0n said:
Saved my ass!
---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------
So do we need to disable modules before updating? The re enable after?
Click to expand...
Click to collapse
Duh what you think? Lol naw for real tho...I've learned that after updating never reinstall mods that aren't up to date with the current os....I can't speak for all mods but magisk roms like renovate ice needs to be updated to the current os or problems will occur....I'm a noobish noob but I learned my lesson

mlock420 said:
Duh what you think? Lol naw for real tho...I've learned that after updating never reinstall mods that aren't up to date with the current os....I can't speak for all mods but magisk roms like renovate ice needs to be updated to the current os or problems will occur....I'm a noobish noob but I learned my lesson
Click to expand...
Click to collapse
Well what I'm getting at is that I deleted all 4 of my magisk mods and fixed the bootloop and then reinstalled all 4 of them and rebooted and everything is fine now. I was asking about should we disable all mods, reboot, update, install magisk, reboot, check root with magisk then reinstall all mods and reboot again?

equlizer said:
Yes i was using it. Just re-installed it.
Click to expand...
Click to collapse
You prob only need to Uninstall that next time b/c that is one that is causing issues. I do not use and I have multiple Modules that survive update not needing to uninstall all modules.

Thanks. I had problem with pernament bootloop after magisk instalation.

Magisk boot.img patching/flashing (Root) with a side of Viper4Android and AdAway

(Problems I had when attempting a "dry" flash and patch:)
Just got the phone today (November 18) then attempted to flash the boot.img after patching it with magisk manager (after magisk patches the boot.img it renames it to "magisk_patched.img"). Got the usb debugging authorized after updating my adb drivers. If you want to make sure your phone is authorized you may need to run commands: adb kill-server and adb devices to check and stop/restart adb.
Anyone able to get it flashed? Getting error:
Code:
FAILED (remote: Failed to write to partition Not Found)
after running
Code:
fastboot flash boot magisk_patched.img
from fastboot, bootloader is unlocked. Running version
Code:
bramble-rd1a.200810.022.a4 (October)
I'd recommend patching up to the November update: Settings, System, System Update to the newest November update (11.0.0 (RD1A.201105.003.C1, Nov 2020).
EDIT: I'd recommend installing 15 second ADB https://forum.xda-developers.com/showthread.php?t=2588979, then overwriting it with the newest adb tools from google. 15 second ADB will add the ADB folder to your system's PATH (ENVIRONMENT VARIABLES) allowing you to run adb commands from any folder (not just the folder adb resides in).
Ok, updating to usb_driver_r13-windows.zip and platform-tools_r30.0.5-windows.zip and updating the build to the Nov RD1A.201105.003.C1 will report back lol
EDIT 2: So yeah, update your drivers and platform tools, successfully patched it:
Code:
fastboot flash boot magisk_patched.img
OUTPUT:
Code:
Sending 'boot_b' (98304 KB) OKAY [ 2.310s]
Writing 'boot_b' OKAY [ 0.480s]
Finished. Total time: 3.122s
How to flash and patch:
https://www.xda-developers.com/google-pixel-4a-how-to-unlock-bootloader-root-pass-safetynet/
Prerequisites:
Download the applicable factory image https://developers.google.com/android/images The Pixel 4A 5G is codenamed "Bramble" (Pull down your shade or look in Settings, "About phone" for Build number) and extract the boot.img from factory image, then transfer it to phone and patch it with magisk manager:
Open Magisk manager -> select ‘Install’ -> ‘Select and Patch File’ -> select your boot.img file
The patched boot image should be found inside your Download folder
After magisk patches it, mount your phone's storage, copy to your computer and flash it from fastboot. Hold down the Power and Volume Down buttons to enter fastboot.
Run command
Code:
fastboot flash boot magisk_patched.img
Platform Tools (includes ADB)
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Usb Drivers
https://dl.google.com/android/repository/usb_driver_r13-windows.zip?hl=ru
Magisk
Direct Link https://github.com/topjohnwu/Magisk/releases/download/v21.1/Magisk-v21.1.zip
Direct Link https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.3/MagiskManager-v8.0.3.apk
Magisk Releases page (in case of an update to magisk or magisk manager) https://github.com/topjohnwu/Magisk/releases/
VIPER4Android (great Digital Signal Processor)
I have been struggling with getting Viper4Android installed.
Stop-gap here:
I flashed this one, but it's distorting my external speakers and is buggy, but it does process...so BE CAREFUL. This will get you there until a more stable version is out. And the video was just taken down. All you have to do is flash it with Magisk here's a link:
https://drive.google.com/file/d/17-NTL0miBYzk4o4v26MstAL9lOPXF3GN/view?usp=sharing
AdAway (system-wide ad blocking)
tried version 5.10 with no luck, let me know if it works for you.
AdAway 4.34 working for me on Android 11.0.0 (RD1A.201105.003.C1, Nov 2020)
Here: https://f-droid.org/repo/org.adaway_40304.apk
AdAway 4.36 (haven't tested)
https://f-droid.org/repo/org.adaway_40306.apk
Make sure to enable "Systemless Hosts" in Magisk Manager before attempting to enable ad-blocking. It's under Settings (the cog/gear in the top right) in the Magisk section.
Good luck all!

Good to see someone working on this. My phone won't be here until tomorrow.
The last time I had trouble flashing, I wasn't running the canary build of Magisk.

Thanks for info and reply on other thread...long time I use this stuff haha
I'm seeing install fail from magisk when I try to patch image .I'm on latest November build
View attachment 5138555

After successfully fastboot unlocking, when I try to patch my boot.img I get the following error from Magisk:
Code:
-Device platform: arm64-v8a
- Copying image to cache
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
! Installation failed
- Repacking boot image
! Unable to repack boot image!
I first tried using the Australian factory image, labelled "11.0.0 (RD1A.201105.003.A1, Nov 2020, AU carriers)" and got the above error.
Then I tried with the Australian + Japan factory image, labelled "11.0.0 (RD1A.200810.020, Oct 2020, AU & JP carriers)" and got the same error.
What fixed it was switching to the BETA update channel in Magisk manager.
Once I changed to the BETA channel I saw in the changelog that they added support for a new boot.img format used by Pixel 5 and Pixel 4a 5G.
Anyone who ends up here from Google, swap to the beta update channel in Magisk manager .

andrew207 said:
After successfully fastboot unlocking, when I try to patch my boot.img I get the following error from Magisk:
Code:
-Device platform: arm64-v8a
- Copying image to cache
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
! Installation failed
- Repacking boot image
! Unable to repack boot image!
I first tried using the Australian factory image, labelled "11.0.0 (RD1A.201105.003.A1, Nov 2020, AU carriers)" and got the above error.
Then I tried with the Australian + Japan factory image, labelled "11.0.0 (RD1A.200810.020, Oct 2020, AU & JP carriers)" and got the same error.
What fixed it was switching to the BETA update channel in Magisk manager.
Once I changed to the BETA channel I saw in the changelog that they added support for a new boot.img format used by Pixel 5 and Pixel 4a 5G.
Anyone who ends up here from Google, swap to the beta update channel in Magisk manager .
Click to expand...
Click to collapse
Thanks for info ..I changed to beta but still having issues patching boot IMG..is this correct Magisk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Do you have a custom recovery installed? I'm trying to figure out how to install Magisk, but I can't find a custom recovery, neither TWRP nor ClockworkMod.

WhiteAsIce said:
Do you have a custom recovery installed? I'm trying to figure out how to install Magisk, but I can't find a custom recovery, neither TWRP nor ClockworkMod.
Click to expand...
Click to collapse
There's no custom recovery. You need to fastboot flash a patched boot.img as described in this guide: https://www.xda-developers.com/googl...ass-safetynet/ using the links from the OP.
Just make sure you're using the latest platform tools, download the matching factory image and change magisk manager to "beta mode" before patching the boot.img.

Android 10 and TWRP
Simma said:
There's no custom recovery. You need to fastboot flash a patched boot.img as described in this guide: https://www.xda-developers.com/googl...ass-safetynet/ using the links from the OP.
Just make sure you're using the latest platform tools, download the matching factory image and change magisk manager to "beta mode" before patching the boot.img.
Click to expand...
Click to collapse
WhiteAsIce said:
Do you have a custom recovery installed? I'm trying to figure out how to install Magisk, but I can't find a custom recovery, neither TWRP nor ClockworkMod.
Click to expand...
Click to collapse
More information on Android 10 and TWRP, though there are some devices slowly getting support for TWRP. Haven't heard clockworkmod in a long time.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html

lmt1979 said:
[...]
Adaway (system-wide ad blocking)
tried version 5.10 with no luck, let me know if it works for you.
Adaway 4.34 working for me on Android 11.0.0 (RD1A.201105.003.C1, Nov 2020)
Here: https://f-droid.org/repo/org.adaway_40304.apk
Adaway 4.36 (haven't tested)
https://f-droid.org/repo/org.adaway_40306.apk
Make sure to enable "Systemless Hosts" in Magisk Manager before attempting to enable ad-blocking. It's under Settings (the cog/gear in the top right) in the Magisk section.
[...]
Click to expand...
Click to collapse
Got v5.1.0 (from F-Droid) working properly with Magisk running with systemless hostfile. Try installing BusyBox (i have v1.32.0 installed) to '/system/bin', which will be used by Adaway (instead of running native commands on root level, which apparently cause the issue).

I can't seem to flash version of Viper in Magisk, it won't let me. I've also tried every combination of the latest viper versions, and their settings, and nothing will run. Perhaps it will on the next version of Magisk. I had posted in the Magisk forum, and none of the suggestions helped.
If anyone has any luck, let us know!

mmarcz said:
I can't seem to flash version of Viper in Magisk, it won't let me. I've also tried every combination of the latest viper versions, and their settings, and nothing will run. Perhaps it will on the next version of Magisk. I had posted in the Magisk forum, and none of the suggestions helped.
If anyone has any luck, let us know!
Click to expand...
Click to collapse
The linked version worked for me after trying the magical downloaded version. I had the audio modification library and audio compatibility modules installed. I don't remember the exact sequence bit all I have now is the posted module l.
It does have some odd issues with file storage. I can save a new preset but putting my old one in the viper folder in internal storage doesn't work. I also can't rename or delete presets. I ended up having to go to /root/storage/self/primary which seems to be internal storage by another path. Pasting my presets in that viper folder worked. No idea how systemless works so can't even guess what's going on.

mmarcz said:
I can't seem to flash version of Viper in Magisk, it won't let me. I've also tried every combination of the latest viper versions, and their settings, and nothing will run. Perhaps it will on the next version of Magisk. I had posted in the Magisk forum, and none of the suggestions helped.
If anyone has any luck, let us know!
Click to expand...
Click to collapse
Just flash the https://drive.google.com/file/d/17-NTL0miBYzk4o4v26MstAL9lOPXF3GN/view?usp=sharing with Magisk. Choose "Modules" the right option on the bottom https://drive.google.com/file/d/1BWLVPtypCjCiqUSEHiRc8sCuMtjqKdY5/view?usp=sharing

lmt1979 said:
Just flash the https://drive.google.com/file/d/17-NTL0miBYzk4o4v26MstAL9lOPXF3GN/view?usp=sharing with Magisk. Choose "Modules" the right option on the bottom https://drive.google.com/file/d/1BWLVPtypCjCiqUSEHiRc8sCuMtjqKdY5/view?usp=sharing
Click to expand...
Click to collapse
Thank you!!!!! Works as advertised!!!!
This was 75% of the reason I bought a pixel!!!
I'm so happy this morning, you have no idea.
It was even processing Amazon music, which didn't work before, so far so good. I only had a chance to listen in the car for 5mins this morning.

mmarcz said:
Thank you!!!!! Works as advertised!!!!
This was 75% of the reason I bought a pixel!!!
I'm so happy this morning, you have no idea.
It was even processing Amazon music, which didn't work before, so far so good. I only had a chance to listen in the car for 5mins this morning.
Click to expand...
Click to collapse
If it stops processing, long press on the icon on the desktop, select App info, Force Stop and reopen and it'll usually start up again. I had to do this much more often on my Pixel 3 than I have on the 4A 5G.

I've followed the steps posted above. Flashed the Drive file in magisk but I'm still getting abnormal status, audio format unsupported. Tips?

VerneVerne said:
I've followed the steps posted above. Flashed the Drive file in magisk but I'm still getting abnormal status, audio format unsupported. Tips?
Click to expand...
Click to collapse
If you're sure you're rooted, some people have noted they needed to use/install Audio Modification Library and possibly Busybox. I'd attempt to clear the cache on Magisk and Viper4Android, as well.
I am on the November build and did not need Audio Modification Library, audio compatibility module (Magisk) or Busybox. I'm using Magisk 21.1 (21180) and Magisk Manager 8.0.3 (314)(14). There's a "puzzle piece" on the far right of the new Magisk Manager menu that has "Install from Storage", this is where I pointed to the Viper.zip and flashed it.

lmt1979 said:
If you're sure you're rooted, some people have noted they needed to use/install Audio Modification Library and possibly Busybox. I'd attempt to clear the cache on Magisk and Viper4Android, as well.
I am on the November build and did not need Audio Modification Library, audio compatibility module (Magisk) or Busybox. I'm using Magisk 21.1 (21180) and Magisk Manager 8.0.3 (314)(14). There's a "puzzle piece" on the far right of the new Magisk Manager menu that has "Install from Storage", this is where I pointed to the Viper.zip and flashed it.
Click to expand...
Click to collapse
Tried all the above. No luck though. I remember it being very finicky on my pixel 3. I'll try again when I'm not actually at work. Thanks for the help though

VerneVerne said:
Tried all the above. No luck though. I remember it being very finicky on my pixel 3. I'll try again when I'm not actually at work. Thanks for the help though
Click to expand...
Click to collapse
I've been glhaving issues too after it worked for awhile. Couldn't deal with no presets thing so tried different Magisks, etc with no luck and now it won't process. I'll update if I find something.
EDIT: the module at https://zackptg5.com/android.php#viper works if run in legacy mode.
EDIT AGAIN: can't save presets for some reason with above module but the ViperFX XDA Labs release before the most current one works in legacy mode https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx

VerneVerne said:
I've followed the steps posted above. Flashed the Drive file in magisk but I'm still getting abnormal status, audio format unsupported. Tips?
Click to expand...
Click to collapse
You need to go into the settings for the app force stop it and then reopen it.

lmt1979 said:
You need to go into the settings for the app force stop it and then reopen it.
Click to expand...
Click to collapse
I've already tried. Started from scratch. Still unsupported status.
Edit: after reading somewhere on here that if you use legacy mode it will process. Followed all steps, set it to legacy and now it works. Thank you everyone

Magisk 22.+ not recognized by Manager, but SU still working on Android 6.0 Marshmallow with Samsung Note 4 SM-N910F TouchWiz, armeabi-v7a

Hi,
Issue with: Magisk 22006 and other 22+
Channel: Canary, but also on others
Plattform: Android 6.0 Marshmallow, armeabi-v7a
Device: Samsung Note 4 SM-N910F
UI: TouchWiz
Recovery: TWRP
Magisk_install_log
- Target image: /dev/block/
- Device platform: armeabi-v7a
- Installing: 66e30a77 (22006)
! Unable to check signature
! Installation failed
- I get this log when I try to install Magisk within the Messenger.
- Patching by TWRP with Devik delete works.
- SU requests afterward pop up properly, may be granted, but are not remembered
Issue 1: Magisk (Manager) does not install/patch within the app, creating that signature error
Issue 2: Magisk (Manager) does not detect patched Magisk, shows only n/a
Issue 3: Magisk (Manager) wants to install current Manager though it is installed
Issue 4: Magisk (Manager) does not offer all features to control SU, hide, etc., though Magisk is patched and SU requests working
Done so far without solving the problem:
- uninstalled/reinstalled Manager
- unpatched/repatched stock boot vi TWRP
- repatched Magisk boot-image
Last Version without these Issues:
Magisk 8.0.7 (pre 22)
Please help, its driving me nuts.

leppit said:
Hi,
Issue with: Magisk 22006 and other 22+
Channel: Canary, but also on others
Plattform: Android 6.0 Marshmallow, armeabi-v7a
Device: Samsung Note 4 SM-N910F
UI: TouchWiz
Recovery: TWRP
Magisk_install_log
- Target image: /dev/block/
- Device platform: armeabi-v7a
- Installing: 66e30a77 (22006)
! Unable to check signature
! Installation failed
- I get this log when I try to install Magisk within the Messenger.
- Patching by TWRP with Devik delete works.
- SU requests afterward pop up properly, may be granted, but are not remembered
Issue 1: Magisk (Manager) does not install/patch within the app, creating that signature error
Issue 2: Magisk (Manager) does not detect patched Magisk, shows only n/a
Issue 3: Magisk (Manager) wants to install current Manager though it is installed
Issue 4: Magisk (Manager) does not offer all features to control SU, hide, etc., though Magisk is patched and SU requests working
Done so far without solving the problem:
- uninstalled/reinstalled Manager
- unpatched/repatched stock boot vi TWRP
- repatched Magisk boot-image
Last Version without these Issues:
Magisk 8.0.7 (pre 22)
Please help, its driving me nuts.
Click to expand...
Click to collapse
I am not used to forums, and this is my debut on xda. I just followed Magisk, noticing I am not allowed as a new member to post about at the canary magisk bug reporting there and was redirected to xda.
Since there is no reply so far, did I do anything wrong, do I have to move the topic somehow?
Thanks for help!

leppit said:
Hi,
Issue with: Magisk 22006 and other 22+
Channel: Canary, but also on others
Plattform: Android 6.0 Marshmallow, armeabi-v7a
Device: Samsung Note 4 SM-N910F
UI: TouchWiz
Recovery: TWRP
Magisk_install_log
- Target image: /dev/block/
- Device platform: armeabi-v7a
- Installing: 66e30a77 (22006)
! Unable to check signature
! Installation failed
- I get this log when I try to install Magisk within the Messenger.
- Patching by TWRP with Devik delete works.
- SU requests afterward pop up properly, may be granted, but are not remembered
Issue 1: Magisk (Manager) does not install/patch within the app, creating that signature error
Issue 2: Magisk (Manager) does not detect patched Magisk, shows only n/a
Issue 3: Magisk (Manager) wants to install current Manager though it is installed
Issue 4: Magisk (Manager) does not offer all features to control SU, hide, etc., though Magisk is patched and SU requests working
Done so far without solving the problem:
- uninstalled/reinstalled Manager
- unpatched/repatched stock boot vi TWRP
- repatched Magisk boot-image
Last Version without these Issues:
Magisk 8.0.7 (pre 22)
Please help, its driving me nuts.
Click to expand...
Click to collapse
Dude I am expecring the exact same issue!!
I fresh installed Rom Marshmallow 6.0.1 on an old Tab. + installed TWRP + old Magisk 21.4. And when I update the Manager to v.22. the same error as you describe appear!!!
Magisk_install_log
- Target image: /dev/block/
- Device platform: armeabi-v7a
- Installing: 66e30a77 (22006)
! Unable to check signature
! Installation failed
Did you finally manage to update the manager/ Magisk Root to v.22 ??

...good to know, I am not alone and my message reached somebody.
But sadly not, still hoping, somebody could help us, or I get permission to post the issue at github.

Yes sure reached ))
Why you want be allowed to post on github, sure you can.
Here is a advice about doing so I goted...
Magisk 22+ not detect and/or crashing on android 6.0.1 arm v7a · Issue #4107 · topjohnwu/Magisk
Device: Samsung Galaxy Note 4 Android version: 6.0.1 Magisk version name: 22 Magisk version code: 22006 Magisk 22+ not detect and/or crashing on android 6.0.1 arm v7a Magisk 21.4 works great. but w...
github.com
it was recommended to me to open a new issue case, Did not had time to try to post...
Anyway can of found a "workaround" only install 21.4, and stay quietly there... after all it is an old device + old ROM, and in my case, I dont use it much... What I found out during all my reseachs , flash/unFlash/ Root/ unRoot/ Backup and Restore ( belive me I tried a lot ), is Magisk do not dance well with old arm +old devices + Marshmallow. I respect a lot the work that is being done around it (Magisk), and it is fine on RECENT MODEL/Roms models I mean...
I said that because I had a second pb, with Booting a restored Backuped on this arm device, and OS is Marshmallow + Magisk Root. You may also check about it
RheinPirat said:
saoudien07 said:
No vbmeta disponible, If I am not wrong it is not for Samaung devices....
I tried all possible combination, when I do the backup, I usually Backup everything, exept Cache. Just in case, always possible to choose what everyone want to restore later...
Then when I restore, I restore: System + Data + Boot. I read System Image is no need, I even tried 3 of them:
Restore with System only, stuck on Splash
Restore with System IMAGE , stuck on Splash
Restore with both ticked, also stuck
Currently I am testing Fresh Rom + TWRP + SuperSU Root (old Root), then Backup and sees if the Restore works...
I already installed SuperSU Root ...
If still Restore pb, I ll go with Fresh Rom + TWRP, only, without any Root of anyKind...
Update:
Magisk is guilty of all my headache!!!!
As I said I tried Fresh Rom + TWRP +SuRoot (old Root method).
Then I backuped, clean everything in TWRP + reboot to TWRP, and restore the Backup just made, and it works flowlessly!!
It seems Magisk is not really going well with old arm device, only assumption here, I am no dev.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Solution: Found out that kind of Magisk to be guilty:
I tried a restore of a Backup: Rom + Magisk + Marshmallow, and it stuck on Boot forever, I decribed about it above...
Finally it was not related to Partition being Restored. Tried a Restore of a Backup ( Rom + SuperSU + Marshmallow) and it works fine. Then tried to restore Backup giving problem, and after restore flash Stock Boot of Marshmallow Rom (Obtained from Stock Rom), and if booted fine to OS.
I even tried Restore + unRoot with Magisk Uninstaller 17.01.2021, and it do not help, should be with Stock Boot !!
So my recommendation for this old device/arm/Marshmallow is, to unRoot the device before to do a Backup!!
At least when you will to restore that made backup, you wont have problem to restore it, as I had, please re-Root, is also an additional flash.....

error

Magisk 21.4 will still work for you OK just don't update the manager to 22 build.
everything has changed from 22 onwards to accommodate newer phones where old methods won't work. flash 21.4 zip, boot and install the manager that goes with it. NEVER UPDATE AGAIN!

3mel said:
Magisk 21.4 will still work for you OK just don't update the manager to 22 build.
everything has changed from 22 onwards to accommodate newer phones where old methods won't work. flash 21.4 zip, boot and install the manager that goes with it. NEVER UPDATE AGAIN!
Click to expand...
Click to collapse
lol, that is what I realized about Magisk, anyway I stay on 21.4 and it is fine for me, less headache

...well, thanks so far.
The reason bothered with 22.00 again and again are my banking apps. Even the last one now detects the old Magisk and quits...
But old Magisk at least lets me access its settings.
You have any hope, they will support oöd phones in future releases and fix the bugs?

leppit said:
You have any hope, they will support oöd phones in future releases and fix the bugs?
Click to expand...
Click to collapse
Of course old devices are supported... So far, Magisk supports Android 4.2+ (from the next release Android 5+). As long as bugs are reported properly they'll be looked into and fixed if possible (unless you've been spamming enough to be banned, you should have full access to submitting issues on GitHub, as long as you follow the issue template).
Example:
This issue was fixed in Canary build 22007 that was released just a couple it days ago.

leppit said:
...well, thanks so far.
The reason bothered with 22.00 again and again are my banking apps. Even the last one now detects the old Magisk and quits...
But old Magisk at least lets me access its settings.
You have any hope, they will support oöd phones in future releases and fix the bugs?
Click to expand...
Click to collapse
yep that its why I prefere stay on 21.4, because the settings is fully accessible and operational.
I noted when updated to v.22, Device is still rooted!! App requiring Root are still functional as supposed to with Root presence, but the issue is with the Manager itself. No more access to settings and so on... and of course they are important!!
About Banking apps, and root detecting, what I use to do, is clean everything and start over from zero.
Some would see this as a placebo, but I pass a run of cleaner before to start over, perso I use SD Maid.
Recently , it helped fix me an other issue with an app, even being uninstalled some of its stuff remain on the phone, and everything was removed, Then, new installation, and the app re-work as expected... So maybe give it a try...
About Magisk, as said devs are always doing there best, so a good report of the issue + log, and everythings appropriated, should of course help them fix the issue.

Didgeridoohan said:
bugs are reported properly
Click to expand...
Click to collapse
Hopefully I finally did so (maybe I missed a bot in the preview, but would be nice, if there were a check before you issue, so it wouldn't hav to be closed and reissued again .... or a at least some examples in the advise... how shall I know which is the proper way to present version name and version code...)
Magisk 22101 (22.+) not detected by Manager ("N/A"), but SU still working on Android 6.0 (+) Marshmallow with Samsung Note 4 SM-N910F TouchWiz, armeabi-v7a and other devices · Issue #4174 · topjohnwu/Magisk
Device: Samsung Note 4, SM-N910F, armeabi-v7a Android version: Android 6.0, Marshmallow Magisk version name: f623b98 Magisk version code: 22101 Full Magisk Version Information: f623b98 (22101) (20)...
github.com

leppit said:
Hopefully I finally did so (maybe I missed a bot in the preview, but would be nice, if there were a check before you issue, so it wouldn't hav to be closed and reissued again .... or a at least some examples in the advise... how shall I know which is the proper way to present version name and version code...)
Magisk 22101 (22.+) not detected by Manager ("N/A"), but SU still working on Android 6.0 (+) Marshmallow with Samsung Note 4 SM-N910F TouchWiz, armeabi-v7a and other devices · Issue #4174 · topjohnwu/Magisk
Device: Samsung Note 4, SM-N910F, armeabi-v7a Android version: Android 6.0, Marshmallow Magisk version name: f623b98 Magisk version code: 22101 Full Magisk Version Information: f623b98 (22101) (20)...
github.com
Click to expand...
Click to collapse
Hi,
I got the same issue as you on my note 4 SM-N910C.
Do I need to boot into TWRP recovery and uninstall the current version of Magisk and re-flash the 21.4 zip file?
Thank you.
Jeffrey
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I installed the 21.4 version and it's working for root access but failed to pass the safetynet checked.
I downloaded the app-debug.apk (Canary) and installed it. It fixed the safetynet checking but loss the Magisk installed app, it backed to the 1st picture "Installed: N/A"
Don't know how to fix it.

Same here. I'm attempting the 21.4 work around. Flashed rooted stock 6.0.1 on verizon Samsung S5, coming from LineageOS 14.1, and attempting Lineage 18.1 from HaggertK.
My main reason for wanting updated Magisk is the use of downloaded modules, such as charge controller, and systemless hosts for ad away.

actionville said:
Same here. I'm attempting the 21.4 work around. Flashed rooted stock 6.0.1 on verizon Samsung S5, coming from LineageOS 14.1, and attempting Lineage 18.1 from HaggertK.
My main reason for wanting updated Magisk is the use of downloaded modules, such as charge controller, and systemless hosts for ad away.
Click to expand...
Click to collapse
Do you able to use the adb or fastboot command? If yes, can share the steps...really appreciate it...tqvm...

try oter third kernel eg. ramkernel

same issue N910F any solution yet?

Guys n gals!
Canyie posted new test build 20 days ago now, but NO-ONE reported testing yet!
https://github.com/topjohnwu/Magisk/issues/4174#issuecomment-985646477
Anyone here still interested in a fix?... Any testers / punters who can send logs?
PW