Introduction: Since the last days I encountered several problems after updating SuperSU (updating from stable 2.79 to 2.80 then 2.81 then finally 2.82).
Refer to https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Also SuperSU (2.80, 2.81) now requires a lot of new permissions not needed for pure root functions, and since it is now owned by Chinese CCMT company,
I prefer another root solution, and discover Magisk and MagiskSU (Magisk/MagiskSU is open source which is excellent for privacy and security).
Magisk official topic: Magisk v12.0 - Root & Universal Systemless Interface [Android 5.0+]
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
All about Magisk:
https://forum.xda-developers.com/apps/magisk
[UNOFFICIAL] Magisk v13 and MagiskManager v5.0 snapshots
https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
I follow the Magisk official topic and try to install Magisk (v12.0 and Magisk manager v4.3.3 from Playstore).
But no root is operational, root is installed but no root persmissions!
After reading some discussion https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382, I decided try the latest Magisk beta (snapshot):
I use:
MagiskManager-v5.0-170612.apk from https://github.com/stangri/MagiskFiles Direct download link: https://github.com/stangri/MagiskFiles/blob/master/MagiskManager-v5.0-170612.apk
Magisk-v13-170612.zip from https://github.com/stangri/MagiskFiles Direct download link: https://github.com/stangri/MagiskFiles/blob/master/Magisk-v13-170612.zip
Magisk-v13-170612-Uninstaller.zip (not needed, just in case) from https://github.com/stangri/MagiskFiles Direct download link: https://github.com/stangri/MagiskFiles/blob/master/Magisk-v13-170612-Uninstaller.zip
UPDATE-unSU-signed.zip from https://forum.xda-developers.com/showpost.php?p=63615067
A2017G-N-B04-boot.img from https://www.androidfilehost.com/?fid=889764386195902948 (original topic: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547 )
A2017G-N-B05-boot.img from https://www.androidfilehost.com/?fid=817550096634782427 (original topic: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547 )
TWRP 3.1.1-0: https://www.androidfilehost.com/?fid=889764386195900705 (original topic: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
And it works, root is OK, root checker passed, and when enabling Magisk Hide in Magisk manager: Safetynet check passed!
This would mean function like Android Pay should be OK too for interested users.
(Add) To get Google Play Store Settings as Certified: select Magisk hide in Magisk manager, check the box corresponding to Play Store, clear Play Store data => certified. So applications like Netflix would be now available in Play Store (they are hidden for rooted (= not certified) phone.
Procedure I followed:
- Current phone status: unlocked bootloader, stock ROM Nougat B04, TWRP recovery 3.1.1-0, root with SuperSU 2.82 (systemless)
- (optional, but recommended for safety) backup with latest TWRP 3.1.1-0: boot, recovery, system, data, cache
- reboot into TWRP, then in this order during same session: install zip UPDATE-unSU-signed.zip, install image A2017G-N-B04-boot.img, install zip Magisk-v13-170528.zip , reboot system => normal boot OK
- Under Android: click on apk to install magisk manager MagiskManager-v5.0-170528.apk (must first enable Unknown sources in Phone Setting/Security) -
- Run MagiskManager: MagiskManager ok, MagiskSU OK!, enable Magisk hide: Safetynet check passed!
- disable "Unknown sources" in phone settings/Security.
Notes:
- If you have SuperSU 2.79, 2.80 or 2.81 this should work too.
- UPDATE-unSU-signed.zip is used to completely remove/uninstall SuperSU first, which helps Magisk install, although Magisk has actions to uninstall
SuperSU by itself.
- This procedure should work too (not tried) for other model like A2017 or A2017U, just be careful to replace the A2017G-N-B04-boot.img boot image with the one corresponding to your model (you could extract boot.img from your model ROM zip).
Edit (add):
- This procedure works also for Nougat B05. Just use A2017G-N-B05-boot.img instead of A2017G-N-B04-boot.img.
- You can use more updated version of Magisk and Magisk Manager.
- If you do not have SuperSU installed, you can skip all steps related to SuperSU.
Uh. How do I download from GitHub?
senny22 said:
Uh. How do I download from GitHub?
Click to expand...
Click to collapse
Well, links to Github are not direct download link, you open it with a browser, then you see a list of apk/zip files with different dates (build).
You then choose a file (for example file with the latest date) by clicking on its name, it will get you to a new page where there is a Download button.
dnlilas said:
Well, links to Github are not direct download link, you open it with a browser, then you see a list of apk/zip files with different dates (build).
You then choose a file (for example file with the latest date) by clicking on its name, it will get you to a new page where there is a Download button.
Click to expand...
Click to collapse
When I press the chosen file (example magisk apk) it brings me to a new page but where the download link is supposed to be it instead says "the file is to big to show". Do I need to be on a PC?
senny22 said:
When I press the chosen file (example magisk apk) it brings me to a new page but where the download link is supposed to be it instead says "the file is to big to show". Do I need to be on a PC?
Click to expand...
Click to collapse
There is in fact a "download" button to download the file. You probably need a PC for this. I will edit the post to add direct download links.
dnlilas said:
There is in fact a "download" button to download the file. You probably need a PC for this. I will edit the post to add direct download links.
Click to expand...
Click to collapse
Got it. Apparently you need a PC.
I tried to install this on V2.0.0B01 chinese.
All passed green except the ctsProfile which returns false.
SU from magisksu works btw. what does ctsProfile mean?
Also, if I tried to enable su for apps and adb, basic integrity gives false too.
@otaconremo
Did you enable Magisk Hide? Maybe this could help:
https://www.youtube.com/watch?v=Bd3GpYd9V5U
dnlilas said:
@otaconremo
Did you enable Magisk Hide? Maybe this could help:
https://www.youtube.com/watch?v=Bd3GpYd9V5U
Click to expand...
Click to collapse
Yes I did enable magisk hide. It's enabled by default and I even toggled it on and off. Also, magisk app force closes whenever I grant su access to any app. But it still does give me su anyway.
To note, v13 is the only version that works on the chinese variant so far. All other previous versions doesn't allow me to boot my device. Maybe because we don't have a custom kernel/boot to begin with.
Any way to use this in the A2017U running b25?
Can you please update files?
dodo34 said:
Can you please update files?
Click to expand...
Click to collapse
Update to latest Magisk files as of today.
ok. i tried it but system is craching inside android.
Thanks, works perfect.
Only SafetyNet check in magisk isnt succesfull.
What to do to pass the check?
When i go on Storage in Settings i get a system carsh error. Is everything ok with your phone ?
Spillunke said:
Thanks, works perfect.
Only SafetyNet check in magisk isnt succesfull.
Click to expand...
Click to collapse
dodo34 said:
When i go on Storage in Settings i get a system carsh error. Is everything ok with your phone ?
Click to expand...
Click to collapse
Yep.
Installed/flashed Magisk 13.3 and now SafetyNet Check works
Thanks :good:. The method worked for me with B05 and Magisk 13.3.
I used the same method with B06. Magisk Manager 13.3 kept crashing but it seems more stable with Magisk 14.0.
Related
Hi guys after trying many apps and xposed module, I kinda found a way how we can save our internal space by saving OBB/DATA files of our games specially the one with large files Don't know if it works on Marshmallow because my unit or model J5007 has no marshmallow bootloader to use 6.0 roms and test this... but if someone is willing to try report here to let the others know I think even though u dont have Magisk, as long as you have root just download Xposed for nougat and find the original flashable zip (not for magisk) then follow the steps
Requirements:
-Magisk Latest v14
-Xposed installer or app for Magisk (main app)
-Xposed v88 SDK 25 (Nougat only) zip for Magisk (install zip)
-OBB ON SD module from Xposed
Steps:
1. Install Magisk v14 or latest from the official forum of it.
2. Install Xposed app for Magisk (main app), Open you will notice that you need to install Xposed
for android 5.1 and up the only way is to flash xposed to install it.
3. Flash Xposed v88 SDK 25 zip then reboot.
4. Open Xposed app (main app) then check if Xposed is installed. if not try flashin again.
5. On Xposed go to Modules then search for OBB ON SD then install and activate it's module.
6. Open OBB ON SD switch on the following: "Data on SD" and "Detect SD on Android 5/6" then others are optional.
7. Copy the OBB/DATA of your game on "sdcard/Android/obb or data" then reboot device and enjoy
Note: Can't post links because i didn't get the owner permission, you could just search them here in XDA
Hit Thanks to thank the developers of Magisk, Xposed, Module and if it helps
@Wood Man and this one...:cyclops:
MOD EDIT @JosephDM: moved!
Thanks! I'll try that soon.
Dont work
I did not get it, it says that the xposed framework is not installed.
Is whatsapp working on external storage through this method???
I posted this a while ago in the [sm-a320fl][7.0][firmware] thread. Now in a new thread, so everybody will find it.
I'm not responsible for any damage. My phone was not branded.
This tutorial is only for SM-A320FL, also known as Galaxy A3!
Make sure you read the whole tutorial before doing anything.
Make a backup of your data. You need to make a factory reset!
Also read the additional information in the separated threads! Knox will be tripped after that, so you can't use it any more. And no more Warranty!
You can find a Android 7 version with the latest security patch with google or just use the linked one. Make sure the CSC is correct for your country/language.
1. Download the following stuff:
Android 7 A320FLXXU1BQH7_A320FLOXA1BQH7_A320FLXXU1BQG6.zip thx to tys0n
Latest Odin3
twrp_3.1.1-1_sm-a320f_11917 thx to ashyx
[*]Boot image patch no-verity-no-encrypt_ashyx thx to ashyx
[*][UNOFFICIAL] Material Design Xposed Installer [09/09/17] thx to DVDandroid
Xposed Installer 3.1.5 thx to rovo89
Magisk thx to topjohnwu
2. Flash Android 7 via Odin. There are enough tutorials on how to do that. Basicly unzip the Android 7 zip file and assign the AP_... file to the AP slot, the BL_... file to the BL slot and so on.
2.a Unlock OEM: Settings -> Developer Options -> OEM unlocking More Information
3. Flash TWRP via Odin; Thread with additional informations
Instructions summary:
Flash with ODIN 3.10.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst holding POWER + HOME.
You should now see TWRP recovery.
Click to expand...
Click to collapse
4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System.
4. Format Data in TWRP. To do that click on Wipe -> Format Data in TWRP. After that all your data is lost! Reboot to System.
5. Copy the Xposed Installer APK file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP.
6. Copy the Magisk ZIP file to your SD card and install it via TWRP. Reboot to System.
7. Open the Magisk Manager and enable root access via SuperUser within the Manager.
8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed.
8. Open Xposed Installer and install the latest Xposed framework. Follow the steps displayed.
9. Now you should have root access, Magisk and Xposed up and running.
Quotes and additional information:
[RECOVERY][ROOT][TWRP 3.1.1-1] Galaxy A3 - SM-A320F/FL/Y (2017) by ashyx
[*][UNOFFICIAL] Material Design Xposed Installer [09/09/17] by DVDandroid
[2017.9.6] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu
[*][2017.9.9][Magisk][SDK 21-25] Xposed v87.3 - Universal Systemless Compatibility by topjohnwu
[OFFICIAL] Xposed for Lollipop/Marshmallow/Nougat/Oreo by rovo89
---------- Post added at 11:22 AM ---------- Previous post was at 11:07 AM ----------
khanvict90 said:
Any body else have lag with the patern unlock screen ?
Click to expand...
Click to collapse
I had the same problem and it drove me crazy. It appeared every time after I rooted my phone with the old "flash the SuperUser.zip via TWRP" method.
After I rooted my phone via Magisk (Tutorial above), there is no more annoying lag. :good:
Trying to install sdk25/sdk25 and getting an error:
Wrong Android version:
This file is for: SDK25
Please download the correct package
for your Android version
Failed
Installation error
simple_s said:
8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed.
Click to expand...
Click to collapse
Anyway, I face the lockscreen lag even if I use Magisk to root my phone. So, sadly no luck for me...
Thanks for the tutorial.
I have two questions.
1. is it needed to use the Xposed installer by DVDandroid, or does the official one do the same job when using Xposed Magisk module?
2. I read you end in a bootloop when using the Magisk way on the Superman ROM thread for S7
https://forum.xda-developers.com/showpost.php?p=74048136&postcount=11120
answer here
https://forum.xda-developers.com/showpost.php?p=74054639&postcount=11125
does this also happen with A320FL? I installed Xposed in system because of that and have no problems.
y2klol said:
Trying to install sdk25/sdk25 and getting an error:
Wrong Android version:
This file is for: SDK25
Please download the correct package
for your Android version
Failed
Installation error
Click to expand...
Click to collapse
Please read the tutorial! You need SDK 24 if you are on Android 7.
Pat750 said:
Thanks for the tutorial.
I have two questions.
1. is it needed to use the Xposed installer by DVDandroid, or does the official one do the same job when using Xposed Magisk module?
Click to expand...
Click to collapse
I didn't try that. Maybe it will work.
Pat750 said:
2. I read you end in a bootloop when using the Magisk way on the Superman ROM thread for S7
https://forum.xda-developers.com/showpost.php?p=74048136&postcount=11120
answer here
https://forum.xda-developers.com/showpost.php?p=74054639&postcount=11125
does this also happen with A320FL? I installed Xposed in system because of that and have no problems.
Click to expand...
Click to collapse
In my opinion it will do the same thing and get stuck in a boot loop. Didn't try it.
simple_s said:
Please read the tutorial! You need SDK 24 if you are on Android 7.
In my message I stated that I tried both sdk24 and sdk25 neither worked. I only posted the error message for sdk25 but it was the same for 24.
Click to expand...
Click to collapse
y2klol said:
Trying to install sdk25/sdk25 and getting an error:
Wrong Android version:
This file is for: SDK25
Please download the correct package
for your Android version
Failed
Installation error
Click to expand...
Click to collapse
y2klol said:
In my message I stated that I tried both sdk24 and sdk25 neither worked. I only posted the error message for sdk25 but it was the same for 24.
Click to expand...
Click to collapse
In your original post you wrote SDK25 twice. So it is not obvious you meant SDK24 and SDK25.
I'm sorry that it didn't work for you. Did you use all the files in the tutorial? What phone do you have and what Android 7 version?
Is it normal that the system takes a while to boot after flashing no verity no encrypt?
Should i hard reset? It is been like 5 mins
ii_Troy said:
Is it normal that the system takes a while to boot after flashing no verity no encrypt?
Should i hard reset? It is been like 5 mins
Click to expand...
Click to collapse
I had the same issue - turns out I missed the formatting step in TWRP.
Before flashing no verity, go to Wipe > Format Data Partition (I cant remember the exact wording)
simple_s said:
In your original post you wrote SDK25 twice. So it is not obvious you meant SDK24 and SDK25.
I'm sorry that it didn't work for you. Did you use all the files in the tutorial? What phone do you have and what Android 7 version?
Click to expand...
Click to collapse
Oh yes, I did. My apologies. It's A5 (2017) and the firmware is A520FXXS2BQJ1 - Galaxy A5 SM-A520F OPS Australia (Optus). Do I have to use the one posted? What is that?
y2klol said:
Oh yes, I did. My apologies. It's A5 (2017) and the firmware is A520FXXS2BQJ1 - Galaxy A5 SM-A520F OPS Australia (Optus). Do I have to use the one posted? What is that?
Click to expand...
Click to collapse
I only tried this tutorial on an A3. Especially the firmware and the TWRP are specialised for the A3. I think the A5 has also quite a different hardware.
Maybe someone in this thread can help you. They root A5:
A5 Root
All works great on my Galaxy A320FL, thanks !!
atlantix1 said:
Anyway, I face the lockscreen lag even if I use Magisk to root my phone. So, sadly no luck for me...
Click to expand...
Click to collapse
its because you fllashed no verify no encrypt this zip should only be flash when you root with super su ...
am i the only one here finding this tutorial poorly written? example:
"4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System."
if you that and you decide to root with magisk you are fked you are gonna face the lock screen delay after you enter the password.
"5. Copy the XposedInstaller_by_dvdandroid_09_09_17.apk file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP."
do we install it?? do we just leave it there???
"8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed. "
witch means = find the module and install it, then enable it, then reboot. now go to exposed and install it then reboot again, now you do have it.
by the way sorry for my bad english .
Hi there.
I found something interesting by accident.
Maybe it is not necessary to install the Xposed Framework via Magisk.
Just use the Magisk Manager as a Super SU replacement and install the Xposed Framework (latest version is 89) directly via the new Xposed Installer (latest version is 3.1.5).
Official Xposed by rovo89
It seems that the phone is running a little bit smoother.
Also it seems that the boot patch is causing some problems.
Maybe the whole tutorial needs to be overlooked. But unfortunately I have now time right now.
nekos95 said:
am i the only one here finding this tutorial poorly written? example:
"4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System."
if you that and you decide to root with magisk you are fked you are gonna face the lock screen delay after you enter the password.
"5. Copy the XposedInstaller_by_dvdandroid_09_09_17.apk file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP."
do we install it?? do we just leave it there???
"8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed. "
witch means = find the module and install it, then enable it, then reboot. now go to exposed and install it then reboot again, now you do have it.
by the way sorry for my bad english .
Click to expand...
Click to collapse
Sorry to hear that. Maybe you can write a new and better one.
simple_s said:
Sorry to hear that. Maybe you can write a new and better one.
Click to expand...
Click to collapse
i kinda just did ... insteed of being ironic you should fix what you did wrong here , you might not realising this but not everyone here has experience to figure things out by himself and your tutorial is causing issues .
nekos95 said:
am i the only one here finding this tutorial poorly written? example:
"4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System."
if you that and you decide to root with magisk you are fked you are gonna face the lock screen delay after you enter the password.
"5. Copy the XposedInstaller_by_dvdandroid_09_09_17.apk file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP."
do we install it?? do we just leave it there???
"8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed. "
witch means = find the module and install it, then enable it, then reboot. now go to exposed and install it then reboot again, now you do have it.
by the way sorry for my bad english .
Click to expand...
Click to collapse
Sorry I have to replay again. I had just a few minutes this morning.
At point 5 I clearly wrote that you have to install the apk!
At point 8 it should be clear that you have to follow the instructions from Xposed. Everybody knows that and has nothing to do with the basic tutorial.
nekos95 said:
i kinda just did ... insteed of being ironic you should fix what you did wrong here , you might not realising this but not everyone here has experience to figure things out by himself and your tutorial is causing issues .
Click to expand...
Click to collapse
Xposed, Root and what not is nothing for beginners. I clearly mentioned that you have to read a lot of stuff. This is not for beginners. Instead of whining and telling me how to do stuff, just write your own thread. Link everything and mention resources. Not everything in this world is baby save. You have to educate yourself!
I overlooked the whole tutorial. I think it is better now and baby save.
Hello,
I cannot get this to work.
Flashing Android 7.0 works
Installing TWRP works
Installing the xposed apk works
but after flashing the magisk zip file i get the message "verification failed" when trying to boot
How can i fix this?
Edit: I managed to fix it. I had to format after install TWRP
BananaOctopus said:
Hello,
I cannot get this to work.
Flashing Android 7.0 works
Installing TWRP works
Installing the xposed apk works
but after flashing the magisk zip file i get the message "verification failed" when trying to boot
How can i fix this?
Edit: I managed to fix it. I had to format after install TWRP
Click to expand...
Click to collapse
Thank you for your help. I updated my phone to the newest Android 7 version today. I had the same problem and solved it with your method. So I implemented this step into the tutorial.
Hi all, I would really appreciate some help in understanding the instructions on installing Magisk root, from this thread: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814 I have already unlocked the bootloader and have highlighted the parts I'm confused about in red:
H. Get HWOTA8_Mate10 Package - I downloaded this.
Magisk
A. Install Magisk by running magisk/magisk.bat and follow instructions. - This I'm stuck on. How do I run magisk.bat. Do I simply have to have the phone connected to PC, and then click the magisk.bat file that is in the HWOTA8 package? Does the phone have to be in fastboot mode. is an adb command involved etc?
B. Install Magisk module (Huawei-Prop-Fix-v1.4_2018012501.zip) to fix background root check and result in safetynet failure. Do I do this after Magisk is installed? So I install Magisk manager apk, then I install this module?
THANKS SO MUCH!
A. You need to have the phone connected to the PC in fastboot. You might need the drivers fix, it can be found in the thread. Just run the bat and follow the instructions.
B. Put the zip in your phone after rooting with Magisk, open the Magisk manager app, slide right go to modules and install the zip. Voil
Safe0716 said:
A. You need to have the phone connected to the PC in fastboot. You might need the drivers fix, it can be found in the thread. Just run the bat and follow the instructions.
B. Put the zip in your phone after rooting with Magisk, open the Magisk manager app, slide right go to modules and install the zip. Voil
Click to expand...
Click to collapse
Thanks a ton Safe0716! I just ran the bat now and believe it was successful. I can see the Magisk manager app has been automatically installed (do I need to install something on top of this?).
I have also loaded the zip file onto internal memory, but before I install that zip as a Magisk module, can I ask what the purpose of that zip is?
The instruction says "Install Magisk module (Huawei-Prop-Fix-v1.4_2018012501.zip) to fix background root check and result in safetynet failure" . The way its written makes it sound like the zip will cause it to result in safetynet failure (for some reason) - or is the purpose of the zip to PREVENT safetynet failure?
Thanks again!
shadders said:
Thanks a ton Safe0716! I just ran the bat now and believe it was successful. I can see the Magisk manager app has been automatically installed (do I need to install something on top of this?).
I have also loaded the zip file onto internal memory, but before I install that zip as a Magisk module, can I ask what the purpose of that zip is?
The instruction says "Install Magisk module (Huawei-Prop-Fix-v1.4_2018012501.zip) to fix background root check and result in safetynet failure" . The way its written makes it sound like the zip will cause it to result in safetynet failure (for some reason) - or is the purpose of the zip to PREVENT safetynet failure?
Thanks again!
Click to expand...
Click to collapse
It's meant to prevent safetynet failure. Without flashing this zip you won't be able to hide root for some apps, let's say you won't be able to use snapchat, netflix etc...
shadders said:
Thanks a ton Safe0716! I just ran the bat now and believe it was successful. I can see the Magisk manager app has been automatically installed (do I need to install something on top of this?).
I have also loaded the zip file onto internal memory, but before I install that zip as a Magisk module, can I ask what the purpose of that zip is?
The instruction says "Install Magisk module (Huawei-Prop-Fix-v1.4_2018012501.zip) to fix background root check and result in safetynet failure" . The way its written makes it sound like the zip will cause it to result in safetynet failure (for some reason) - or is the purpose of the zip to PREVENT safetynet failure?
Thanks again!
Click to expand...
Click to collapse
It adds checks that Magisk doesn't check for. Basically Huaweis own props. So it "prevents" failure. It doesn't force safetynet to say OK even though it would fail otherwise, it just adds props to check for that otherwise would make safetynet fail.
And to add to your questions, all bats by mankindtw tell you what to do when you run them, in case you want to use HWOTA8 in the future to update or rebrand.
Safe0716 said:
It's meant to prevent safetynet failure. Without flashing this zip you won't be able to hide root for some apps, let's say you won't be able to use snapchat, netflix etc...
Click to expand...
Click to collapse
Thanks for helping me out Safe0716 I appreciate it I installed the zip and it seems to pass SafetyNet so I'm all set with root (the process was a lot more involved than previous phones I've had but its finally done). Its just a shame that we can't go further and install xposed on this phone!
shadders said:
Thanks for helping me out Safe0716 I appreciate it I installed the zip and it seems to pass SafetyNet so I'm all set with root (the process was a lot more involved than previous phones I've had but its finally done). Its just a shame that we can't go further and install xposed on this phone!
Click to expand...
Click to collapse
Yeah unfortunately it isn't working yet, but I'm sure somebody will figure it out !
ante0 said:
It adds checks that Magisk doesn't check for. Basically Huaweis own props. So it "prevents" failure. It doesn't force safetynet to say OK even though it would fail otherwise, it just adds props to check for that otherwise would make safetynet fail.
And to add to your questions, all bats by mankindtw tell you what to do when you run them, in case you want to use HWOTA8 in the future to update or rebrand.
Click to expand...
Click to collapse
Thanks for that info, I now have a better understanding. And ah in terms the bats, yes I saw when I clicked on it that it did indeed have helpful instructions! But I assumed there was certain things I had to do before running it, e.g. fastboot mode, and so was scared to click on it!
Should be helpful in the future. Now that I am rooted with Magisk, does that mean I can no longer accept OTAs and updates will have to go through HWOTA8? If so, will updating through HWOTA8 wipe the system, or preserve user data? Thanks!
shadders said:
Thanks for that info, I now have a better understanding. And ah in terms the bats, yes I saw when I clicked on it that it did indeed have helpful instructions! But I assumed there was certain things I had to do before running it, e.g. fastboot mode, and so was scared to click on it!
Should be helpful in the future. Now that I am rooted with Magisk, does that mean I can no longer accept OTAs and updates will have to go through HWOTA8? If so, will updating through HWOTA8 wipe the system, or preserve user data? Thanks!
Click to expand...
Click to collapse
I haven't received any yet... But I tend to update as soon as an update is pushed to http://pro-teammt.ru/firmware-database/
which is long before it's actually pushed to the public (long being 2 weeks+).
Userdata is preserved when you update FullOTA updates and bootloader remains unlocked. So you just need to reflash Magisk after it's done updating.
Magisk data (modules) is kept too as that's kept in /data/
Instructions to Install ViPER4Android on Android Oreo
The instructions have been split into two parts for your convenience. The first part involves setting up the device before you proceed to the actual instructions to install ViPER4Android on Android Oreo 8.0. The second part covers installing ViPER4Android itself and the drivers.
Step 1: Pre-setup
Download and install Busybox on your rooted Android. V4A team recommend using Stephen (Stericson) Busybox, so download it by clicking on the app box below.
BusyBox
Stephen (Stericson) Tools FreeDownload
Once it has been installed on your device, launch the app from the app drawer.
As soon as the app starts, it will prompt you for root permissions, so grant them.
Install ViPER4Android on Android Oreo - Busybox Installation
Install ViPER4Android on Android Oreo – Busybox Installation
Make sure that you are in the “Install Busybox” tab. Do not modify any options, leave them as they are.
Tap on the “Install” button on the very bottom of the app screen. The Busybox installation will start and complete in no time. You shall see the confirmation message instantly.
Next, download a root-enabled file manager of your choice. We prefer Solid Explorer for its simplicity and efficiency.
Solid Explorer File Manager
NeatBytes Productivity FreeDownload
Once installed, launch Solid Explorer.
Swipe out from the left edge of the app screen and tap on “Root” under the “Storages” menu.
Install ViPER4Android on Android Oreo - Give Root permissions to Solid Explorer
Install ViPER4Android on Android Oreo – Give Root permissions to Solid Explorer
The app will prompt for root permissions, grant them.
Navigate to /Vendor/etc. Find the file named “audio_effects.conf”.
Long-press on the file, then tap on the 3-dot overflow menu on the top-right and select “Rename”.
Change the filename to “audio_effects.conf.bak“. You could have simply deleted the file, but we advise you to rename it so that if you want to restore in future, it will spare you some trouble.
Install ViPER4Android on Android Oreo - Rename "audio_effects.conf" file in /vendor/etc
Install ViPER4Android on Android Oreo – Rename “audio_effects.conf” file in /vendor/etc
Just tap on “OK” and exit the Solid Explorer.
Finally, the last thing to do is set SELinux status as Permissive. We can do that easily using “The SELinux Switch” app. So, download the app and install it on your device – The.SELinux.Switch.ver.6.0.3.build.603.apk. Then launch the app, grant it root permissions, and press the “Permissive” button. If you find it troublesome, you can simply follow our tutorial.
Just reboot your device. It is very important to reboot after you have performed the above.
Step 2: Install ViPER4Android on Android Oreo
Now that you have properly setup your Android device to install ViPER4Android on Android Oreo, follow the steps below.
Download ViPER4Android for Android Oreo: ViPER4Android_FX_v2505.zip
Extract the downloaded file. You shall then have two files:
ViPER4Android_FX_v2505_A4.x-A7.x.apk
ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk
We are only going to need the latter (ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk).
Connect your device to the PC and transfer the file to it.
Install ViPER4Android on Android Oreo - Install ViPER4Android app
Install ViPER4Android on Android Oreo – Install ViPER4Android app
Now open Solid Explorer (Or any other file explorer). Navigate to the location where you placed the *.apk file and install it.
Once installed, go to the app drawer and tap on “ViPER4Android”.
As soon as the app is launched, it will prompt you for driver installation.
Just tap on “YES”. You shall instantly be asked for root permissions, so grant them.
Install ViPER4Android on Android Oreo - Driver Installation
Install ViPER4Android on Android Oreo – Driver Installation
The driver installation will begin and your phone’s screen will freeze. Don’t worry, it’s going as planned. Do not exit the app or press any buttons.
After 30-60 seconds the process will complete. Simply tap on “OK” and reboot your device.
Once your phone has rebooted, open the V4A app again and swipe out from the left to open the menu.
Install ViPER4Android on Android Oreo - Driver Status
Install ViPER4Android on Android Oreo – Driver Status
Select “Driver Status”. It should display the status value as “Normal”. You are now ready to give a nice push to your phone’s audio experience by customizing settings in the ViPER4Android app.
I just installed the magisk module and works perfect [emoji848] View attachment 4427228
Enviado desde mi SM-G955F mediante Tapatalk
markoelprototipo said:
I just installed the magisk module and works perfect [emoji848] View attachment 4427228
Enviado desde mi SM-G955F mediante Tapatalk
Click to expand...
Click to collapse
If you listen carefully you will notice that with the Magisk module you do not get changes when you activate the different configurations. And instead with this method everything is working in the best way. Thank you for your comments!
adriano222 said:
If you listen carefully you will notice that with the Magisk module you do not get changes when you activate the different configurations. And instead with this method everything is working in the best way. Thank you for your comments!
Click to expand...
Click to collapse
I tested all configurations and works perfect
markoelprototipo said:
I tested all configurations and works perfect
Click to expand...
Click to collapse
Well in that case remains as an alternative for those who do not work well the other method. Regards!:bueno::RE
viperfx for s7 edge oreo rom
adriano222 said:
Instructions to Install ViPER4Android on Android Oreo
The instructions have been split into two parts for your convenience. The first part involves setting up the device before you proceed to the actual instructions to install ViPER4Android on Android Oreo 8.0. The second part covers installing ViPER4Android itself and the drivers.
Step 1: Pre-setup
Download and install Busybox on your rooted Android. V4A team recommend using Stephen (Stericson) Busybox, so download it by clicking on the app box below.
BusyBox
Stephen (Stericson) Tools FreeDownload
Once it has been installed on your device, launch the app from the app drawer.
As soon as the app starts, it will prompt you for root permissions, so grant them.
Install ViPER4Android on Android Oreo - Busybox Installation
Install ViPER4Android on Android Oreo – Busybox Installation
Make sure that you are in the “Install Busybox” tab. Do not modify any options, leave them as they are.
Tap on the “Install” button on the very bottom of the app screen. The Busybox installation will start and complete in no time. You shall see the confirmation message instantly.
Next, download a root-enabled file manager of your choice. We prefer Solid Explorer for its simplicity and efficiency.
Solid Explorer File Manager
NeatBytes Productivity FreeDownload
Once installed, launch Solid Explorer.
Swipe out from the left edge of the app screen and tap on “Root” under the “Storages” menu.
Install ViPER4Android on Android Oreo - Give Root permissions to Solid Explorer
Install ViPER4Android on Android Oreo – Give Root permissions to Solid Explorer
The app will prompt for root permissions, grant them.
Navigate to /Vendor/etc. Find the file named “audio_effects.conf”.
Long-press on the file, then tap on the 3-dot overflow menu on the top-right and select “Rename”.
Change the filename to “audio_effects.conf.bak“. You could have simply deleted the file, but we advise you to rename it so that if you want to restore in future, it will spare you some trouble.
Install ViPER4Android on Android Oreo - Rename "audio_effects.conf" file in /vendor/etc
Install ViPER4Android on Android Oreo – Rename “audio_effects.conf” file in /vendor/etc
Just tap on “OK” and exit the Solid Explorer.
Finally, the last thing to do is set SELinux status as Permissive. We can do that easily using “The SELinux Switch” app. So, download the app and install it on your device – The.SELinux.Switch.ver.6.0.3.build.603.apk. Then launch the app, grant it root permissions, and press the “Permissive” button. If you find it troublesome, you can simply follow our tutorial.
Just reboot your device. It is very important to reboot after you have performed the above.
Step 2: Install ViPER4Android on Android Oreo
Now that you have properly setup your Android device to install ViPER4Android on Android Oreo, follow the steps below.
Download ViPER4Android for Android Oreo: ViPER4Android_FX_v2505.zip
Extract the downloaded file. You shall then have two files:
ViPER4Android_FX_v2505_A4.x-A7.x.apk
ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk
We are only going to need the latter (ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk).
Connect your device to the PC and transfer the file to it.
Install ViPER4Android on Android Oreo - Install ViPER4Android app
Install ViPER4Android on Android Oreo – Install ViPER4Android app
Now open Solid Explorer (Or any other file explorer). Navigate to the location where you placed the *.apk file and install it.
Once installed, go to the app drawer and tap on “ViPER4Android”.
As soon as the app is launched, it will prompt you for driver installation.
Just tap on “YES”. You shall instantly be asked for root permissions, so grant them.
Install ViPER4Android on Android Oreo - Driver Installation
Install ViPER4Android on Android Oreo – Driver Installation
The driver installation will begin and your phone’s screen will freeze. Don’t worry, it’s going as planned. Do not exit the app or press any buttons.
After 30-60 seconds the process will complete. Simply tap on “OK” and reboot your device.
Once your phone has rebooted, open the V4A app again and swipe out from the left to open the menu.
Install ViPER4Android on Android Oreo - Driver Status
Install ViPER4Android on Android Oreo – Driver Status
Select “Driver Status”. It should display the status value as “Normal”. You are now ready to give a nice push to your phone’s audio experience by customizing settings in the ViPER4Android app.
Click to expand...
Click to collapse
Hello, sir im trying to install viper4android on samsung s7 edge G935FD im using oreo 8.0 (samsung experience 9) offical vietnam rom i got this rom from this website.
i did same as you told to do to install viperfx but the problem is there is no file named as ''audio_effect.conf'' in root/Vendor/etc
in root/vendor/etc there is a file named as audio_effects_common.conf.
and if i go to root/system/etc there i can see these two files ''audio_effects.conf'' and ''audio_effects_sec.conf''
and as you said to rename ''audio_effects.conf'' as ''audio_effects.conf.bak'' i did this but after doing this when i open viper it says tap yes to install drivers when i tap yes it says ''driver install failed: the busybox installation found on your device doesnot work. this usually means you installed a wrong or broken busybox. V4A needs stericson's busybox to work.if you are sure you installed the proper busybox,then please confirm your device has been completely rooted.''
and my root is fine and even busybox is installed properly i guess actually error comes when i rename the ''audio_effect.conf'' to ''audio_effect.conf.bak'' and if i rename it back to ''audio_effect.conf'' then it doesnot show me this error but it keeps on asking my to install driver again and again please help me it been more then 18 hours im trying to install viperfx but i cant do it
im a music love i managed to get a good headphone but without viper4android music dont feell that good
No download links dor busybox
---------- Post added at 11:23 PM ---------- Previous post was at 11:20 PM ----------
I can't find download links for busybox
M seeing only audio_effects.xml and audio_policy.conf
Which 1 shld i rename??
Phenomenali'm said:
M seeing only audio_effects.xml and audio_policy.conf
Which 1 shld i rename??
Click to expand...
Click to collapse
This is the friend file!:good:
wasaymirza said:
Hello, sir im trying to install viper4android on samsung s7 edge G935FD im using oreo 8.0 (samsung experience 9) offical vietnam rom i got this rom from this website.
i did same as you told to do to install viperfx but the problem is there is no file named as ''audio_effect.conf'' in root/Vendor/etc
in root/vendor/etc there is a file named as audio_effects_common.conf.
and if i go to root/system/etc there i can see these two files ''audio_effects.conf'' and ''audio_effects_sec.conf''
and as you said to rename ''audio_effects.conf'' as ''audio_effects.conf.bak'' i did this but after doing this when i open viper it says tap yes to install drivers when i tap yes it says ''driver install failed: the busybox installation found on your device doesnot work. this usually means you installed a wrong or broken busybox. V4A needs stericson's busybox to work.if you are sure you installed the proper busybox,then please confirm your device has been completely rooted.''
and my root is fine and even busybox is installed properly i guess actually error comes when i rename the ''audio_effect.conf'' to ''audio_effect.conf.bak'' and if i rename it back to ''audio_effect.conf'' then it doesnot show me this error but it keeps on asking my to install driver again and again please help me it been more then 18 hours im trying to install viperfx but i cant do it
im a music love i managed to get a good headphone but without viper4android music dont feell that good
Click to expand...
Click to collapse
Were you able to find a fix for this? I'm having the same issues, and cannot find a solution. Thanks!
Sagoode said:
Were you able to find a fix for this? I'm having the same issues, and cannot find a solution. Thanks!
Click to expand...
Click to collapse
Same goes here
Can any one here post mi notes app for PE and other custom ROMs or do any one know any way around to install it on custom roms.
installing fake MIUI Framework Module in Magisk may mock apk files to think the device is running on MIUI and not on Custom Rom
P/s: i have not tested this theory!
YasuHamed said:
installing fake MIUI Framework Module in Magisk may mock apk files to think the device is running on MIUI and not on Custom Rom
P/s: i have not tested this theory!
Click to expand...
Click to collapse
while your idea seems logical i dont have the technical knowledge to test this theory ..can you explain the procedure or guide me to a suitable read
bravo2526 said:
while your idea seems logical i dont have the technical knowledge to test this theory ..can you explain the procedure or guide me to a suitable read
Click to expand...
Click to collapse
while you are in Magisk,
1. open download section from swipe left
2. search for MIUI framework
3. download it / let magisk patch it
4. reboot device
5. download miui notes from apkmirror .com and try installing.
if it doesnt work you can always go back to magisk and remove/delete installed module(s) and magisk will remove it when device will reboot next time
YasuHamed said:
while you are in Magisk,
1. open download section from swipe left
2. search for MIUI framework
3. download it / let magisk patch it
4. reboot device
5. download miui notes from apkmirror .com and try installing.
if it doesnt work you can always go back to magisk and remove/delete installed module(s) and magisk will remove it when device will reboot next time
Click to expand...
Click to collapse
let me try this ...thankx for the input
bravo2526 said:
let me try this ...thankx for the input
Click to expand...
Click to collapse
Is it working!?