Database Develop

Can't install SuperSU updated binary

Hey,
I've just rooted my phone for the first time recently. I have a Lenovo S960 so the task wasn't easy.. almost nobody has support for this kind of phone. Ended up using Kingroot. Root Checker tells me all is OK and if I use a terminal, I can switch to and browse as root, so it seems like my phone is indeed rooted.
However, I cannot get write privileges on my /system directory (the main reason why I rooted was so that I could remove all the bloatware which comes with Lenovo phones). If I try to mount it via a terminal it just says "mount: read-only file system" and if I use Root Explorer, when I press "Mount as R/W" in /system, nothing happens.
I read on the internet that I should get SuperSU and grant superuser privileges or something among the lines. So I went to google play and installed SuperSU and when I opened it it told me I needed to update SuperSU binary files and it lets me choose between installing it via recovery or normal. If I choose normal it just tells me that the installation has failed. So I installed CWM recovery (tried first with TWRP but that wouldn't recognize my SD card for some reason). If I go into the SuperSU app and choose "TWRP/CWM" as an installation method it tells me "SuperSu will attempt to reboot your device into recovery. This might not work for all devices" and, indeed, nothing happens. So I manually boot into recovery mode looking for a SuperSU binaries file anywhere, but I couldn't find one. I then downloaded SuperSUv2.6.zip from the internet and flashed it manually (which took a while to figure out since the menu is in Chinese). When I boot up my device, the SuperSU app is now gone (and of course I still can't grant write privileges on /system). I try to install SuperSU from google play again and I run into the exact same situation as before.
Any help would be appreciated.
Thanks in advance.
P.S: I got my zip from a thread here named [STABLE][2015.02.13] SuperSU v2.46; not sure if I can post links here but a search should reveal this thread if anyone is interested. I've also tried downloading it from different sources but it was the exact same file (same md5).

I'm having the same problem with my HTC One M8. Got the v2.46 update but it won't install. I cleared the cache within recovery and it just wipes the phone again. Not a big deal, but there's gotta be something within the structure of the file directories that let it install the old SuperSU that isn't the same with the v2.46 update. I'm still looking into it. E-mail if you figured it out, [email protected]

I have seeder fail ask root with super su 2,64 - Android revolution hd room. I tried to flash latest supersu but still issue HTC-oNe m8 too

jk

Hi I'm having same problem on. lg k7 (lgms330)

Distant1 said:
Hi I'm having same problem on. lg k7 (lgms330)
Click to expand...
Click to collapse
I obtained root today on the MetroPCS K7. Root with kingroot. Apk v4.50 and use older version of SuperSUme (not the current one on Play) to change to SuperSU and delete all the kingroot crap. Reboot after rooting with kingroot then use SuperSUme... No errors here... Updated binary and installed busybox.

Shaun_vip said:
I obtained root today on the MetroPCS K7. Root with kingroot. Apk v4.50 and use older version of SuperSUme (not the current one on Play) to change to SuperSU and delete all the kingroot crap. Reboot after rooting with kingroot then use SuperSUme... No errors here... Updated binary and installed busybox.
Click to expand...
Click to collapse
Ty

"Wolfdroid script" will help with that GOOGLE IT..... ITS VERY SIMPLE..u just bssically use the kingroot to grant ur terminal and SUPERSU root permissions to remove it...kinda setting itself up to fail and be replaced..Harsh in a sense but affective..an evil plot...hahaha

Shaun_vip said:
I obtained root today on the MetroPCS K7. Root with kingroot. Apk v4.50 and use older version of SuperSUme (not the current one on Play) to change to SuperSU and delete all the kingroot crap. Reboot after rooting with kingroot then use SuperSUme... No errors here... Updated binary and installed busybox.
Click to expand...
Click to collapse
By any chance do you know if there's a custom recovery for lg k7 floating around online?

At the time I obtained root, no. Not sure if one had been made or not.

actually I have the same problem.but I use stock rom (official rom from Sammobie)
android 4.4.2 and I don't have recovery cwm or twrp (it's long story).
the point is: how to root my device with this problem?
not/ I use galaxy s3 verizon

supersu not able to provide root permissons : Android 6.0.1
Hi,
I am currently working on an automation task, where i need to provide root access to other supporting apps. But as I am not able to provide the root access the app crashes with an error message as "Unfortunately xyz app has stopped". This was found working with Android L with older supersu app but not working with Android 6.0 with the latest marshmellow version of the supersu app.
Device : It is a test device hence cannot share any data about the product (Sorry for the inconvenience)
OS : Android 6.0.1
SuperSu app version : have tried with v2.37, v2.56 and v2.67
Kindly help us and ASAP @Chainfire : hope chainfire is reading this

KingRoot rooted my LG K7 and installed Superuser. The Binaries needed updating for SuperSU, so I found the stable SuperSU v2.46, which was already saved from Chainfire on Twitter earlier on my PC(Link not found but here is Chainfire's)https://download.chainfire.eu/696/SuperSU/, and placed it on my ext SD Card, got flashify from Google Play and flashed it into Internal. Since there is contravercy about which Recovery's are compatible with this device. Then deleted ALL files except KingRoot and SuperSU. (King User, KingaRoot, Superuser, and all else I could find and have forgot) All seems well at this point.
Reading and studying for a recovery and possibly my first custom ROM.
NOTE: only v2.46 worked on some of my devices, newer versions/updates did nothing without the SuperSU v2.46 being previously flashed.

charliew410 said:
KingRoot rooted my LG K7 and installed Superuser. The Binaries needed updating for SuperSU, so I found the stable SuperSU v2.46, which was already saved from Chainfire on Twitter earlier on my PC(Link not found but here is Chainfire's)https://download.chainfire.eu/696/SuperSU/, and placed it on my ext SD Card, got flashify from Google Play and flashed it into Internal. Since there is contravercy about which Recovery's are compatible with this device. Then deleted ALL files except KingRoot and SuperSU. (King User, KingaRoot, Superuser, and all else I could find and have forgot) All seems well at this point.
Reading and studying for a recovery and possibly my first custom ROM.
NOTE: only v2.46 worked on some of my devices, newer versions/updates did nothing without the SuperSU v2.46 being previously flashed.
Click to expand...
Click to collapse
Which K7 do you have Metro or T-MO? a friend gave me this phone to do something nice with it. Phone only for Music Freedom on the 30$ 5GB plan. Having Viper FX would be nice.

patt2k said:
Which K7 do you have Metro or T-MO? a friend gave me this phone to do something nice with it. Phone only for Music Freedom on the 30$ 5GB plan. Having Viper FX would be nice.
Click to expand...
Click to collapse
It is the Metro PCS Device. And now that I have my 16 gig S4 operational again, maybe I will be playing with the 2 K7's that I have to see what I can come up with.
---------- Post added at 04:58 AM ---------- Previous post was at 04:56 AM ----------
mirfan4 said:
Hi,
I am currently working on an automation task, where i need to provide root access to other supporting apps. But as I am not able to provide the root access the app crashes with an error message as "Unfortunately xyz app has stopped". This was found working with Android L with older supersu app but not working with Android 6.0 with the latest marshmellow version of the supersu app.
Device : It is a test device hence cannot share any data about the product (Sorry for the inconvenience)
OS : Android 6.0.1
SuperSu app version : have tried with v2.37, v2.56 and v2.67
Kindly help us and ASAP @Chainfire : hope chainfire is reading this
Click to expand...
Click to collapse
As I said before only Super SU 2.4.6 have I had luck with updating the binaries.
---------- Post added at 05:03 AM ---------- Previous post was at 04:58 AM ----------
Death_Gun said:
actually I have the same problem.but I use stock rom (official rom from Sammobie)
android 4.4.2 and I don't have recovery cwm or twrp (it's long story).
the point is: how to root my device with this problem?
not/ I use galaxy s3 verizon
Click to expand...
Click to collapse
I just rooted an S4 with Kingroot, had the problem of binaries not installed with Super SU , installed Super sume, ran it,(which uninstalls Kingroot) and Super SU popped up again asking for the binaries, clicked yes, and normal installation and done.

Hi guys, problem as following.
I've a LG G3 running cyanogenmod 13 for a couple of months also updated it.
I haven't needed root access for a while, but now I need it for an app, but it was gone. So I opened SuperSU and I wanted to reactivate root.
But I have problems with the binarys. I can't install them via the app not the twrp.
In the help section it says me to download an apk called supersume but I cannot find this.
Could u help me?
Sebastian
{
"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"
}
Gesendet von meinem LG-D855 mit Tapatalk

[ViPER4AndroidFX][AudioMod] Install Latest ViPER4AndroidFX_v2.5.0.5 on Any ROMs

{
"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'M NOT RESPONSIBLE IF YOUR DEVICE IS NOT BOOTING UP, DEVICE IS BRICKED, GOT BOOTLOOPED OR WHATEVER ***​*** DO AT YOUR OWN RISK ***​*** READ AND UNDERSTAND EACH AND EVERY STEPS CAREFULLY BEFORE PROCEEDING ***​
The most commonly used Audio modification tool among the Android users is ViPER4Android. It has been making audio clearer and more perceptible on millions of Android devices out there. Today here, I will be guiding you on how to Install ViPER4Android on any ROM in your devices.
After months and months of no activity, the Viper4Android developer zhuhang has finally announced the official 2.5.0.5 update. While primarily, the update aims at enabling users to install ViPER4Android on Nougat 7.x.x, it also incorporates some new features.
Code:
CHANGELOG:
New App icon, package name, and UI
Added cross-channel (“quad channel”) convolver support.
This allows faithful reproduction of sound-field effects requiring such cross-channel convolution, such as simulation of speaker soundfield on headphones, or crosstalk cancellation (stereo widening) on stereo speakers.
Added FET compressor (new compressor / limiter simulating operation of FET circuits)
Support for custom settings storage path (no more looking everywhere in the phone for the settings directory!)
Miscellaneous bug fixes.
Code:
BUILD INFORMATION:
Version: FX version 2.5.0.5 (active)
Codename: (FX version) Beautiful
Compiled date: September 1,2016 / September 4,2013 – Official Release
Operating environment: Android 2.3 / 4.0 / 4.1 / 4.2 / 4.3 / 4.4 / 5.0 / 6.0 / 7.0/7.1/7.1.2
CPU platforms: ARM (ARM CortexA8 or higher), x86(Atom/i3/i5/i7)
Language: English (US) / Simplified Chinese / Traditional Chinese / more
​
Warning -
Installing incorrect/incompatible mods on your Android device could be harmful. Please make sure that you are aware of the outcome and don’t forget to take a Nandroid backup of your current ROM before proceeding. DroidOrigin or any of its members shall not be held liable for any damage to your device. However, if you’re stuck, we will still try to pull you out of any troubles.[/CENTER]
Installing Viper4Android is pretty simple, given that you meet the requirements pre-hand. If you have found yourself in a sticky situation, then the steps below could be of help too.
Requirement -
Rooted Device.
TWRP recovery.
BusyBox 1.26.2
ES File Explorer or Any Root File Browser.
NOTE :​There are two files provided in the download section below. One is for manually installing and another one is for directly flashing through twrp. Please download any one file whichever you want and then follow the correct steps for that file only. Before proceeding, please check whether you have downloaded the manual installation file or flashable file. If you have downloaded the manual installation file then follow the procedures for manually installing the app & drivers and if you have downloaded the flashable zip file then follow the procedures for flashing the zip file through TWRP and then installing the driver.​
Steps For Manually Installing ViPER4Android in your device-
1. Now that you have everything setup correctly, download the official ViPER4Android for Nougat (FX 2.5.0.5) from below.
2. Extract the downloaded zip and it will contain two apks –
ViPER4Android_FX_v2505_A4.x-A7.x.apk
ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk
3. Since we are going to install Viper4Android on Nougat, we will just need the “ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk” file.
4. If you have downloaded it to your PC instead, just transfer the apk to your phone’s storage.
5. Before we head to the installation, open the ES File Explorer and grant it root permissions when prompted.
6. Open ES File Explorer and browse to the location where the apk is present. Copy the “ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk” file and move it to “/system/priv-app“.
7. We are not done yet. Long-press the file, tap on the 3-dot overflow button, and select Properties. And set its permission to -rw-r–r–, and select APPLY.
8. Reboot your device now.
9. Now go to the app drawer and run the ViPER4Android FX app. When you are asked for storage permissions, make sure to grant them.
10. A prompt will display for driver installation. Select Yes to confirm the driver installation process. You will also need to allow Superuser (root) permissions to the app.
11. Your phone’s screen may freeze, don’t worry just wait and do not exit the app. Your android system will popup that app is not responding, just press wait button. Let the app finish it's driver installation, so don't exit the app now. When the installation is successful, you will get a message. Tap OK and reboot your device.
When your device reboots, you will have completely functional ViPER4Android on Nougat and other Android versions.
If you have trouble in driver installation, read the troubleshooting section below or comment right away.
Steps For Installing ViPER4Android through TWRP in your devices
1. Download the flashable zip file from below (Filename - ViPER4Android_2.5.0.5 (Flashable))
2. Reboot to recovery.
3. Flash the ViPER4Android_2.5.0.5 (Flashable).zip file.
4. Reboot system.
5. When device is booted up properly, then open the ViPER4Android app.
6. If it will ask root permission then grant the root permission.
7. It will popup a message for installing the driver. Just tap ok and wait for installing the driver.
8. Your phone’s screen may freeze, don’t worry just wait and do not exit the app. Your android system will popup that app is not responding, just press wait button. Let the app finish it's driver installation, so don't exit the app now. When the installation is successful, you will get a message. Tap OK and reboot your device.
When your device reboots, you will have completely functional ViPER4Android on Nougat and other Android versions.
NOTE : PLEASE DISABLE YOUR DEFAULT MUSICFX OR AUDIOFX IN ORDER TO USE ViPER4AndroidFX​
Credits -
zhuhang for developing the ViPER4Android
ViPER4Android Team
and many more.
(If I have missed anyone's name then please PM me for that)
You can download the ViPER4Android FX_version2.5.0.5 from below. Please follow the steps properly otherwise you will end up with problems.

Troubleshooting -​
If your driver installation has failed, then there could be few reasons behind it. Follow the simple steps below and check if anything helps.
Getting “Driver instal failed: I/O error, please reboot and try again”? Then read step again.
Uninstall the current busybox and switch to a different app to install busybox on your Android.
The most reliable and widely used method to root and manage permissions is SuperSU. If you’re using any other root method, uninstall that and opt for SuperSU.
Driver installation was successful, but V4A is still not working? The most common reason behind this is that your device may have other sound mods or tweaks installed. Disable them and completely remove them if possible.
On some devices, you may require to change your SELinux status from “Enforcing” to “Permissive”. You can do that by using the SELinuxToggler.
If nothing above has worked for you, then you may try switching to a different ROM as your last resort.
If you still have problems, comment below and don’t forget to mention your device model, ROM, and Android version.

reserved

reserved 2

do we still need busybox?

emirfahimi said:
do we still need busybox?
Click to expand...
Click to collapse
Without busybox you can't install viper4android. You have to install the latest busybox.

Hey bro , i use lineage os rom and i get driver install failed eventhough i change different busybox ..

not working it says cannot detect root and failed to install driver

emirfahimi said:
not working it says cannot detect root and failed to install driver
Click to expand...
Click to collapse
First root your device, then install the busybox. After that install the viper4android.

raven001 said:
Hey bro , i use lineage os rom and i get driver install failed eventhough i change different busybox ..
Click to expand...
Click to collapse
Please check the troubleshooting post.
Otherwise try this busybox which is shown in the screenshot below -

juyel92 said:
First root your device, then install the busybox. After that install the viper4android.
Click to expand...
Click to collapse
i did exactly as the step my phone is already rooted

emirfahimi said:
i did exactly as the step my phone is already rooted
Click to expand...
Click to collapse
Please check in devloper menu whether the root access is enabled for both adb & apps.

juyel92 said:
Please check the troubleshooting post.
Otherwise try this busybox which is shown in the screenshot below -
Click to expand...
Click to collapse
Still not work bro ,,

juyel92 said:
Please check in devloper menu whether the root access is enabled for both adb & apps.
Click to expand...
Click to collapse
yes it is adb and apps but its working other app such as free dom or lucky patcher can be used and i'm pretty sure root is working on my zenfone 5

raven001 said:
Still not work bro ,,
Click to expand...
Click to collapse
What error you are getting?

emirfahimi said:
yes it is adb and apps but its working other app such as free dom or lucky patcher can be used and i'm pretty sure root is working on my zenfone 5
Click to expand...
Click to collapse
Can you please share the screenshot of that error ?

juyel92 said:
What error you are getting?
Click to expand...
Click to collapse
This

juyel92 said:
Can you please share the screenshot of that error ?
Click to expand...
Click to collapse
View attachment 4131491

raven001 said:
This
Click to expand...
Click to collapse
I will check this issues.
Please give me some time. I will soon update/fix this issues.

I will soon fix these issues. Till then please wait and be patient.

[Release][2022.6.26] Magisk Manager for Recovery Mode (mm)

Magisk Manager for Recovery Mode v7 202206260
I updated VR25's Magisk Manager for Recovery mode so it now also works with Magisk v19.0 - v25.X!
With this you can be at ease while trying out Android Magisk Modules.
Since if you end up with a bootloop you can just disable the module from recovery
Saved my ass many times!
- Source code
- Documentation
- Releases
- Original thread
Note: The GUI "Magisk Manager Recovery Tool" project is a different, stand-alone project.
Which is not affiliated with this CLI "Magisk Manager for Recovery Mode" project.
Edit1: Reported as working on Magisk v23.X! Updated the documentation and released a new version
Edit2: Tested and confirmed working on Magisk v25.X! Updated the module's readme, print lines, inner docs...

I might be doing something wrong but it's not working...
{
"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"
}
Poslano z mojega MI 9 z uporabo Tapatalk

mxxt01 said:
I might be doing something wrong but it's not working... View attachment 4997015
Poslano z mojega MI 9 z uporabo Tapatalk
Click to expand...
Click to collapse
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.

Rikj000 said:
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.
Click to expand...
Click to collapse
Sorry, all clear now [emoji16]
I was just about to try in TWRP...
Thanks!
Poslano z mojega MI 9 z uporabo Tapatalk

Rikj000 said:
Magisk Manager for Recovery v5 202004170
I updated VR25's Magisk Manager for Recovery mode so it now also works with Magisk v20.X!
With this you can be at ease while trying out Android Magisk Modules.
Since if you end up with a bootloop you can just disable the module from recovery
Saved my ass many times!
Flash this in TWRP each time you want to use it, not in Magisk itself.
You can download the new release from my GitHub: https://github.com/Rikj000/mm/releases/tag/2020.4.17
Original thread: https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
Click to expand...
Click to collapse
Thanks this will be handy when experimenting some modules
Sent from my Mi A2 using Tapatalk

Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support

JamesKinds said:
Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support
Click to expand...
Click to collapse
Are you sure you downloaded and installed my updated version? v5 (2020.04.17)
Because that was the error I was getting with the original v4 (2019.04.04) and the reason I made this new release. Be sure you're downloading from my GitHub fork

JamesKinds said:
Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support
Click to expand...
Click to collapse
Same here.
Updater process ended with error: 123

Rikj000 said:
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.
Click to expand...
Click to collapse
The old 2019 version sticks for me & I had no issues whatsoever installing it from TWRP on Magisk v20.x setup. I can still do /sdcard/mm from TWRP terminal & do stuff.
Sorry if I'm unable to see what's the purpose of this 'fork'.
Sent from my #FlagshipKiller6T using Tapatalk

DarkSJ1998 said:
The old 2019 version sticks for me & I had no issues whatsoever installing it from TWRP on Magisk v20.x setup. I can still do /sdcard/mm from TWRP terminal & do stuff.
Sorry if I'm unable to see what's the purpose of this 'fork'.
Click to expand...
Click to collapse
Updated installer script to support the latest magisk. It's unclear to me how you managed to get v4 installed though, me and other users where having issues with it on magisk v20, check the latest comments on the original thread.
All I wanted to do was to be able to use this piece of software again since it saved my skin a lot of times already... If you don't trust my change feel free to review my commits on github, it's all open source
Other benefit to it is that the original didn't have a release / easy and clear instructions, which is the cause of this module being less popular then it should be. I hope my new release clears up that problem aswell.

Rikj000 said:
Are you sure you downloaded and installed my updated version? v5 (2020.04.17)
Because that was the error I was getting with the original v4 (2019.04.04) and the reason I made this new release. Be sure you're downloading from my GitHub fork
Click to expand...
Click to collapse
Hi,
Unless I'm making a mistake, I'm using the ZIP file from here:
https://github.com/Rikj000/mm/releases/tag/2020.4.17
Am I using the wrong file?

JamesKinds said:
Hi,
Unless I'm making a mistake, I'm using the ZIP file from here:
https://github.com/Rikj000/mm/releases/tag/2020.4.17
Am I using the wrong file?
Click to expand...
Click to collapse
Nope that should be the right file, please make sure that the zip doesnt have spaces in it's name and don't flash this in Magisk, flash it in TWRP

Rikj000 said:
Nope that should be the right file, please make sure that the zip doesnt have spaces in it's name and don't flash this in Magisk, flash it in TWRP
Click to expand...
Click to collapse
Weird, all criteria mentioned are met. Would the fact that I have an existing installation of mm perhaps trigger the problem?

JamesKinds said:
Weird, all criteria mentioned are met. Would the fact that I have an existing installation of mm perhaps trigger the problem?
Click to expand...
Click to collapse
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.

Magisk v20.4 ERROR 123 ((( for Recovery

Latest Magisk Canary, working like a charm, thanks

Rikj000 said:
Updated installer script to support the latest magisk. It's unclear to me how you managed to get v4 installed though, me and other users where having issues with it on magisk v20, check the latest comments on the original thread.
All I wanted to do was to be able to use this piece of software again since it saved my skin a lot of times already... If you don't trust my change feel free to review my commits on github, it's all open source
Other benefit to it is that the original didn't have a release / easy and clear instructions, which is the cause of this module being less popular then it should be. I hope my new release clears up that problem aswell.
Click to expand...
Click to collapse
I've done a couple of clean flashing in these weeks & I could install the old one via TWRP effortlessly. I'm also on Magisk v20.4 (have tried it using Magisk v20.3 & lower versions as well) & running Android 10.
IDK why you guys are facing issues...
Sent from my #FlagshipKiller6T using Tapatalk

DarkSJ1998 said:
I've done a couple of clean flashing in these weeks & I could install the old one via TWRP effortlessly. I'm also on Magisk v20.4 (have tried it using Magisk v20.3 & lower versions as well) & running Android 10.
IDK why you guys are facing issues...
Click to expand...
Click to collapse
Upon further inspection might be due to spaces in the zip file name. But magisk script wasnt up to date anyways. So this version will be supported in Magisk for a longer time then the original due to that.

Rikj000 said:
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.
Click to expand...
Click to collapse
Bro, uninstall all versions this mod, reboot system, boot to twrp flash zip, go in twrp to terminal write mm, write q and click enter, boot to system, reboot to twrp go to terminal and type sdcard/mm important sdcard/mm, now should work

Rikj000 said:
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.
Click to expand...
Click to collapse
I found the solution to the installation error eventually. The zip itself MUST be somewhere in internal storage when flashing and cannot be in sd card or otg. And even the old mmfr zip installs for me if I place it in internal storage. So maybe include this in your post. For context, I use Android Q rom with Magisk 20.4.

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