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/
Related
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.
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.
Hello everyone, I have a problem on which audio enhancement to use? I tried to install Viper4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk, but it does not install the necessary drivers, my problem is that I use Spotify and the sound is very simple, I would need to strengthen the bass a little bit, I have the B&O headphones.
Thanks
the best audio package by far is A.R.I.S.E.
I use magisk, but it should work with SuperSU too.
You need to have busybox installed to /system/xbin for Viper4Arise to work properly.
When you flash the ARISE package the first time, it will drop a file "arise_customize.conf" into /sdcard
This is what you use to customize which ARISE modules you want to be installed when you flash the ARISE installer the second time.
I have attached the arise_customize.conf file that I use, and know works very well on LG-V20.
For many reasons, though, I recommend looking into switching to magisk over supersu.
After you have busybox installed properly, and after you have Viper4ARISE flashed properly with the customize file used, there is a module in the magisk app repository "universal_deep_buffer_remover".. this is the ONLY thing I have found that correctly removes the deep buffer without breaking the HIFI dac on the V20.
(you can also easily install busybox from the magisk manager app too, although I recommend flashing that module from recovery first. You may need to play with that its triicky. Install from recovery and/or from within the magisk manager app.)
it should go without saying that before you start installing this you will need to remove any other audio mods that you have installed previously, or the best bet being reflash your ROM to get a fresh start.
syndre said:
the best audio package by far is A.R.I.S.E.
I use magisk, but it should work with SuperSU too.
You need to have busybox installed to /system/xbin for Viper4Arise to work properly.
When you flash the ARISE package the first time, it will drop a file "arise_customize.conf" into /sdcard
This is what you use to customize which ARISE modules you want to be installed when you flash the ARISE installer the second time.
I have attached the arise_customize.conf file that I use, and know works very well on LG-V20.
For many reasons, though, I recommend looking into switching to magisk over supersu.
After you have busybox installed properly, and after you have Viper4ARISE flashed properly with the customize file used, there is a module in the magisk app repository "universal_deep_buffer_remover".. this is the ONLY thing I have found that correctly removes the deep buffer without breaking the HIFI dac on the V20.
(you can also easily install busybox from the magisk manager app too, although I recommend flashing that module from recovery first. You may need to play with that its triicky. Install from recovery and/or from within the magisk manager app.)
it should go without saying that before you start installing this you will need to remove any other audio mods that you have installed previously, or the best bet being reflash your ROM to get a fresh start.
Click to expand...
Click to collapse
You forgot to attach the file
Looking forward to it, I've always used Viper and never heard of this one, I'm eager to try it.
UL7RA said:
You forgot to attach the file
Looking forward to it, I've always used Viper and never heard of this one, I'm eager to try it.
Click to expand...
Click to collapse
so sorry, my fault
I did attach the file but I didn't see that it rejected the .prop extension, I edited that first post with it uploaded as a text file, same file is attached here too. Remove the .txt and put it on /sdcard
If you open the file and change the install core to =true, you will only have to flash the arise zip once (instead of letting it place that customize.prop file on SD card the first time around).
syndre said:
so sorry, my fault
I did attach the file but I didn't see that it rejected the .prop extension, I edited that first post with it uploaded as a text file, same file is attached here too. Remove the .txt and put it on /sdcard
If you open the file and change the install core to =true, you will only have to flash the arise zip once (instead of letting it place that customize.prop file on SD card the first time around).
Click to expand...
Click to collapse
Unfortunately, I believe not much of ARISE works on my H990DS, as the first time I flashed using your prop file, I got arkamys audio to continuously force close. Uninstalled it by editing the prop file, reboot. Tried opening Dolby Atmos, force close. I guess I'm left with Viper, which I've had before anyway. I'm on magisk, if that matters, but I saw that the magisk compatibility was set to true.
UL7RA said:
Unfortunately, I believe not much of ARISE works on my H990DS, as the first time I flashed using your prop file, I got arkamys audio to continuously force close. Uninstalled it by editing the prop file, reboot. Tried opening Dolby Atmos, force close. I guess I'm left with Viper, which I've had before anyway. I'm on magisk, if that matters, but I saw that the magisk compatibility was set to true.
Click to expand...
Click to collapse
If you're using SuperSU the only other thing that I could think of would be making sure BusyBox is installed
In the future if something like that is force closing you can either just freeze the application or delete the app folder in system partition using recovery.
If you haven't yet tried flashing your ROM again, letting boot up and sit for a few minutes, then flash busybox and arise again on a fresh ROM installation, that is definitely something to try.
I'm just curious, is there a reason why you prefer SuperSU over magisk?
I use the BusyBox flashable installer made by as from here. He's got lots of other neat things on that thread to!
https://forum.xda-developers.com/showthread.php?t=2239421
Sent from my LG V20 using XDA Labs
syndre said:
If you're using SuperSU the only other thing that I could think of would be making sure BusyBox is installed
In the future if something like that is force closing you can either just freeze the application or delete the app folder in system partition using recovery.
If you haven't yet tried flashing your ROM again, letting boot up and sit for a few minutes, then flash busybox and arise again on a fresh ROM installation, that is definitely something to try.
I'm just curious, is there a reason why you prefer SuperSU over magisk?
I use the BusyBox flashable installer made by as from here. He's got lots of other neat things on that thread to!
https://forum.xda-developers.com/showthread.php?t=2239421
Sent from my LG V20 using XDA Labs
Click to expand...
Click to collapse
No, I'm not using SuperSU, I'm on Magisk (14.0). You might have missed when I said that. BusyBox is installed and running fine, and I managed to fix everything by flashing the ARISE zip, but with a modified prop file.
UL7RA said:
No, I'm not using SuperSU, I'm on Magisk (14.0). You might have missed when I said that. BusyBox is installed and running fine, and I managed to fix everything by flashing the ARISE zip, but with a modified prop file.
Click to expand...
Click to collapse
ahh ok, yeah misunderstood that you got it going
great
Sent from my LG V20 using XDA Labs
Hello, thanks for replying ... I installed my system again with MagiskSU, but when I installed ARISE, I could not understand how to install it ... I downloaded the MAGNUS OPUS package and tried to flash with the TWP, and there was ERROR 1, I put both your "arise_customize.prop" in my sdcard (/sdcard/arise_customize.prop) and what is in the ARISE forum, but without success ...
let's go to the beginning ... first I install MagiskSU, then BusyBox, then I put the file on sdcard? and then try to install? that's what i did
what am I doing wrong?
Thanks for the cooperation
pkrename said:
Hello, thanks for replying ... I installed my system again with MagiskSU, but when I installed ARISE, I could not understand how to install it ... I downloaded the MAGNUS OPUS package and tried to flash with the TWP, and there was ERROR 1, I put both your "arise_customize.prop" in my sdcard (/sdcard/arise_customize.prop) and what is in the ARISE forum, but without success ...
let's go to the beginning ... first I install MagiskSU, then BusyBox, then I put the file on sdcard? and then try to install? that's what i did
what am I doing wrong?
Thanks for the cooperation
Click to expand...
Click to collapse
The order I flash those things is first the ROM (if your ROM has any audio mods included as separate zips in the main rom zip, most modded stock roms do this, remove that. Either delete any viper or dolby zips from the main rom zip, or comment out the libes that install them in the update-script FIRST).
Second I flash busybox, it should say "installng to /system/xbin".
Third I flash Magisk. The current latest version is v14.5 and I can confirm it works n my V20.
After that, I boot into the rom and let it up the stock audio configuration to and confirm that you have sound working initially. After it settles down for a few minutes, I go back into recovery and then flash the arise zip.
The first time you flash ARISE, it checks to see if the customize prop file is present on/ sdcard and if it is it will use those options. If the customize file is not present the only thing it will do is install the core part of ARISE, and it will place that customize.prop file onto /sdcard for you. If that happens you'll get a message saying so, instructing you to edit it to select which modules you want. The customize.prop file I attached is what I use, you don't necessarily have to use those exact settings, you can choose what you want and play around with it and see what works. Trial and error is a way of life doing these mods.
Flashing the same ARISE zip a second time once you edited the prop file to your liking will install what you choose instead of just the core files.
Reboot back into your ROM and open the magisk manager app. You'll notice there is a module there for ARISE compatibility. At this point your equalizer apps should be functioning, but only for local media files. To get the sound to process through the Viper equalizer using streaming music you need to remove the deep audio buffer. Magisk manager allows you to do this very easily by just downloading the universal deep audio remover module from the repository in magisk manager.
While you're at this point, it's a good idea to also download and install the BusyBox module from the magisk manager app too. You can install the magisk BusyBox module on top of what you already flashed in recovery, thats how I do it. If there's any conflicting files the magisk module takes priority. If anything, doing this gives me the peace of mind that BusyBox is for sure installed correctly.
After installing the BusyBox and deep buffer remover modules from the magisk manager app, reboot and that should be it! The only thing you need to do now to take your already amazing DAC to the next level is adjust the equalizer settings to what you like. This is a never ending quest to make whatever youre listening to sound perfect. Frustrating but fun at the same time.
Of course there are a ton of things that could go wrong, each case seems to be different, so there's no way to let you know what to do before a problem shows up.
Try that and let me know how it goes. Good Luck!
syndre said:
The order I flash those things is first the ROM (if your ROM has any audio mods included as separate zips in the main rom zip, most modded stock roms do this, remove that. Either delete any viper or dolby zips from the main rom zip, or comment out the libes that install them in the update-script FIRST).
Second I flash busybox, it should say "installng to /system/xbin".
Third I flash Magisk. The current latest version is v14.5 and I can confirm it works n my V20.
After that, I boot into the rom and let it up the stock audio configuration to and confirm that you have sound working initially. After it settles down for a few minutes, I go back into recovery and then flash the arise zip.
The first time you flash ARISE, it checks to see if the customize prop file is present on/ sdcard and if it is it will use those options. If the customize file is not present the only thing it will do is install the core part of ARISE, and it will place that customize.prop file onto /sdcard for you. If that happens you'll get a message saying so, instructing you to edit it to select which modules you want. The customize.prop file I attached is what I use, you don't necessarily have to use those exact settings, you can choose what you want and play around with it and see what works. Trial and error is a way of life doing these mods.
Flashing the same ARISE zip a second time once you edited the prop file to your liking will install what you choose instead of just the core files.
Reboot back into your ROM and open the magisk manager app. You'll notice there is a module there for ARISE compatibility. At this point your equalizer apps should be functioning, but only for local media files. To get the sound to process through the Viper equalizer using streaming music you need to remove the deep audio buffer. Magisk manager allows you to do this very easily by just downloading the universal deep audio remover module from the repository in magisk manager.
While you're at this point, it's a good idea to also download and install the BusyBox module from the magisk manager app too. You can install the magisk BusyBox module on top of what you already flashed in recovery, thats how I do it. If there's any conflicting files the magisk module takes priority. If anything, doing this gives me the peace of mind that BusyBox is for sure installed correctly.
After installing the BusyBox and deep buffer remover modules from the magisk manager app, reboot and that should be it! The only thing you need to do now to take your already amazing DAC to the next level is adjust the equalizer settings to what you like. This is a never ending quest to make whatever youre listening to sound perfect. Frustrating but fun at the same time.
Of course there are a ton of things that could go wrong, each case seems to be different, so there's no way to let you know what to do before a problem shows up.
Try that and let me know how it goes. Good Luck!
Click to expand...
Click to collapse
Great Tutorial... but... in my phone... (H990DS) with custom root by DirtySanta, the Magisk v14.5 make this device no boot... does it work with version 14.0?
I have a LS997 and also see dirty santa. I run Schwifty's kernel, if that is of any interest to you.
Yes, v14 will be fine to use.
This is for anyone doing audio mods, check out sauron ainur audio, it's a Russian team that figured out a new/better way to mod devices,, (any variant) I've tried bout everything, and it is way better than arise, guitarded hero even chimed in on the forum and credited them as the real deal and not a poser basically, the bass is much tighter and puncher and tunable, must have magisk and u can have other mods along with it e.g.--v4a, James dsp, Arkamys, Dirac, etc. Read the thread!!! And it's easier to install. It will/is change android modding imo.
I was able to do it, but I only managed to release it on my device after upgrading to version 14.5... in version 14 it did not run... I did all the steps as it happened in my tutorial and now it is running the perfect V4A !! Thank you syndre was a great help!
I used to think arise was best, all magisk users should try sauron ainur audio mod, the only one I got to activate is the mk II beta 8. Easy to install if you follow directions and can use viper and other mods with it, they found a new way to do audio mods that's changing the game for audio it just ain't well known yet, read the thread, guitarded hero chimes in and validates them as the real deal and I can say it is awesome, tighter bass, clearer w/less congestion from non working/compatible ports. Message me if you need help or have general questions. Can be tricky to learn, (me anyway since I just started using magisk). Russian team I believe, try it out, good luck.
---------- Post added at 01:40 AM ---------- Previous post was at 01:34 AM ----------
Beta 8 was only one i could get to activate quad dac, wanted to correct that, but the versions without dac activated still sound better than other mods with dac working, it's that good. Imo the bass is way more tunable and precise, and punchier which is important to me.
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!?
This thread is now defunct. I have moved to iPhone. Sorry about this.
Take care everybody.
Regards,
Magnetox
Appreciate this! If I'm already unlocked, is it possible to remove the -w in the flash-all script before running for a rooted install without wiping user data?
Wi1son said:
Appreciate this! If I'm already unlocked, is it possible to remove the -w in the flash-all script before running for a rooted install without wiping user data?
Click to expand...
Click to collapse
I would leave it as is, but if you want to try it, go ahead (might brick).
Hi ! Thanks for it.
Just a question After flash the Rom when the phone reboot before copy magisk manager can restore my Google backup ?
And how I do when they had an update ?
Thanks
ggkameleon said:
Hi ! Thanks for it.
Just a question After flash the Rom when the phone reboot before copy magisk manager can restore my Google backup ?
And how I do when they had an update ?
Thanks
Click to expand...
Click to collapse
Yes that should be fine. Just restore normally. But don't forget magisk otherwise it won't have proper root.
Might be a silly question, but, does this stock image work with Google Fi?
Also, a little confused with some of the directions...
In step 1 it says "Download the appropriate rar package for your system and install."
Does this mean download my stock image from Google and install it with Magisk, or... ?
In step 9 it says, " Once in fastboot, and the bootloader, run "fastboot devices" from the "BRAMBLE" folder. "
Does this mean to run "fastboot devices" as a command inside the command prompt from the "BRAMBLE" folder or to open one of the tools inside the platform tools folder?
Also, in step 11, where do I find the "appropriate flash-all command on your operating system"?
These are just a bit confusing to me. Don't want to brick my phone, so any help is appreciated.
Thanks
SpecialKCF22 said:
Also, a little confused with some of the directions...
...
Thanks
Click to expand...
Click to collapse
Download the WinRAR package in the mega.nz folder for your OS.
Both, platform tools should be in that BRAMBLE folder. Example fastboot.exe should be in BRAMBLE.
You will find this in your BRAMBLE folder when you properly extract platform tools and the .rar into the BRAMBLE folder.
SpecialKCF22 said:
Might be a silly question, but, does this stock image work with Google Fi?
Click to expand...
Click to collapse
It's just stock with root, so if the Pixel 4a 5g works normally it will too.
Magnetox said:
Download the WinRAR package in the mega.nz folder for your OS.
Both, platform tools should be in that BRAMBLE folder. Example fastboot.exe should be in BRAMBLE.
You will find this in your BRAMBLE folder when you properly extract platform tools and the .rar into the BRAMBLE folder.
Click to expand...
Click to collapse
You're not very detailed and you didn't answer the questions. I'll pass on this method. Thanks
SpecialKCF22 said:
You're not very detailed and you didn't answer the questions. I'll pass on this method. Thanks
Click to expand...
Click to collapse
Feel free to PM
Magnetox said:
Yes that should be fine. Just restore normally. But don't forget magisk otherwise it won't have proper root.
Click to expand...
Click to collapse
So, will update delete the magisk app? Or what do you mean when write "don't forget magisk"?
Ryav said:
So, will update delete the magisk app? Or what do you mean when write "don't forget magisk"?
Click to expand...
Click to collapse
I mean don't forget to install it and assure you have proper root after.
Does this one works with Google pay. My rooted build of RD1A.200810.022.A4 doesn't pass the safety check on magisk manager. Thank you
imFonk said:
Does this one works with Google pay. My rooted build of RD1A.200810.022.A4 doesn't pass the safety check on magisk manager. Thank you
Click to expand...
Click to collapse
MAGISK MODULE ❯ Universal SafetyNet Fix 1.1.0
Thanks for this! FYI for anyone curious the newest Magisk 8.07 does work, you don't need to use the linked file.
dadozer said:
Thanks for this! FYI for anyone curious the newest Magisk 8.07 does work, you don't need to use the linked file.
Click to expand...
Click to collapse
Yes feel free to do this. The APK that is linked works fine as well and will update itself with your permission.
Magnetox said:
Hey everybody,
Here is the latest Android 11 January 2021 update rooted (I will keep it updated). It's all clean. It is the Google stock system image with root applied (comes with GAPPS). You can cleanly flash your device with this as long as your fastboot (bootloader) is working.
Download LINK:
File folder on MEGA
mega.nz
Steps:
1) Download the appropriate rar package for your system and install.
2) Download the appropriate platform-tools package for your operating system (this contains ADB and Fastboot) and extract it in a folder we'll call "BRAMBLE" (we will use this folder for the install).
3) Download the bramble-rq1a.210105.003.rar file (this is the stock rom). Extract it to the "BRAMBLE" folder. You will want to see all the files (ie. the flash-all.sh) all in the folder the same folder that contains the ADB and Fastboot tools.
4) Download MagiskManager-v8.0.4.apk, this will be used after the install and installed on the device.
5) Enable USB debugging and OEM unlocking (the bootloader unlock) in developer options (smash on build a bunch of times in a row real fast to enable developer options in about phone).
7) Navigate to the "BRAMBLE" folder with a terminal or command prompt (depending on your operating system) and run "adb devices" with root or administrator access in your terminal or command prompt on your computer (respectively there). Allow the USB debugging to connect to your computer forever on your phone, something should pop up. It should appear in the terminal or command prompt. If not you need to accept USB debugging on your phone (forever).
8) Put in the command "adb reboot bootloader" once your device appears.
9) Once in fastboot, and the bootloader, run "fastboot devices" from the "BRAMBLE" folder. This should return your device. If not, something is wrong and restart. Another way of reaching fastboot is restarting your phone and holding VOLUME DOWN.
10) Make sure your device is unlocked, run "fastboot flashing unlock".
11) In the "BRAMBLE" folder, run the appropriate flash-all command on your operating system. This will take a while and completely reflash the system with the Stock ROM with root. You will see the progress as it appears.
12) Once it's done, your phone will reboot. Just wait for it to start up and do as you normally would on a new flash.
13) Move the MagiskManager-v8.0.4.apk onto the phone, and install it. It will confirm you have partial root and ask you to apply something more and reboot. Do so.
14) When rebooted, your phone will be fully flashed and rooted. Feel free to download a root verification app, I recommend this one. It should be working fine. Grant root permission forever to it.
If you have any questions, feel free to ask. You can install the ElementalX kernel on this rom for Pixel 4a 5g. Download this. It's a great kernel tool and it will help you with full root access download and install the kernel. It's the kernel I'm using.
Regards,
Magnetox
Click to expand...
Click to collapse
i could not install magisk, the 13th step in your guide might not be complete.
i managed to root, and got to pass safety net, and google pay working.
i have to move the boot.img from the zip file included in the package you provided, move it to internal storage, patch it in magisk manager.
then i moved the patched boot.img to my pc, did adb reboot bootloader, then fastboot flash [patched boot.img] and then only i was fully rooted.
i also flash the safetynet-fix-v1.1.1.zip module in magisk to pass satefynet.
hope it could help out, i digged all night yesterday to get this done lol.
MegaJuif said:
i could not install magisk, the 13th step in your guide might not be complete.
i managed to root, and got to pass safety net, and google pay working.
i have to move the boot.img from the zip file included in the package you provided, move it to internal storage, patch it in magisk manager.
then i moved the patched boot.img to my pc, did adb reboot bootloader, then fastboot flash [patched boot.img] and then only i was fully rooted.
i also flash the safetynet-fix-v1.1.1.zip module in magisk to pass satefynet.
hope it could help out, i digged all night yesterday to get this done lol.
Click to expand...
Click to collapse
I updated it with the latest 8.0.7 magisk. Hope this fixes it. (Uploading now)
Upload complete! (Magisk 8.0.7)