[QUESTION] [H990] [V10i][DIRTYSANTA] [SUPERSU] Which Audio Booster root? - LG V20 Themes, Apps, and Mods

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.

Related

[TUTORIAL] How to remove ads with AdAway

Since removing ads from browser and apps was one of the main reasons to root my DX I decided to make this tutorial. Problem is you can't just install AdAway (link) and run it because after a reboot you'll have to do it again. This method is keeping the ads away even after a reboot. Remember that you'll have to update AdAway-hosts files regularly.
All credits go to Yasir Javed Ansari. I only finetuned the method he described a little bit. Because his post is somewhere in another thread it seemed right to make a tutorial for it in the themes and apps section.
First of all you'll need a properly rooted DX with superuser 3.1.3 installed. See here for a zip to install superuser and busybox or here to download a pre-rooted 1.18 stock deodexed rom with superuser and busybux installed provided by infernal77. I'm using this rom on my DX and removed a lot of bloatware with Aroma (link) right after flashing the rom. Credits go to merovig for sharing info about flashable superuser/busybox-zip and Aroma and of course to infernal77 for providing his deodexed stock rom. Although it seems that this method shouldn't be necessary when using a deodexed rom I couldn't get it to work without using the command lines, so I decided to share it anyway.
In settings - power, uncheck 'fast boot'.
Install AdAway from Play Store. Run AdAway (don't download hosts files yet) and go to settings - preferences. Check 'allow redirections' and under 'target hosts file' select '/data/data/hosts'.
Reboot to recovery and then mount /system and mount /data.
While in recovery-mode connect the device to a PC and open a command prompt.
Type:
adb shell
cd system/etc
rm hosts
ln -s /data/data/hosts hosts
Disconnect the device from PC and reboot.
Now you can run AdAway: download files and apply ad blocking.
Done!
Nice one, added to Index.
@op, Good job.
Although my tutorial was word by word the same, apart from maybe few spelling mistakes. ;p
Above is required for Stock Rom which is rooted.
On custom and rooted Rom , you don't need to perform above steps as system is write permitted so running ad away normally works fine.
Regards
Yasir
Sent from my HTC Desire X
Hehe I know, the only thing I added was the /etc
Problem is that when I install for example infernals rooted stock deodexed rom, and then I install AdAway and hosts files, they don't survive a reboot. When I redirect the hosts file to /data/data/hosts AdAway states it can't create the symlink. That's why I still use your method even on a pre-rooted rom.
nightcrow said:
Hehe I know, the only thing I added was the /etc
Problem is that when I install for example infernals rooted stock deodexed rom, and then I install AdAway and hosts files, they don't survive a reboot. When I redirect the hosts file to /data/data/hosts AdAway states it can't create the symlink. That's why I still use your method even on a pre-rooted rom.
Click to expand...
Click to collapse
This symlink method(not mine) is present in ad away FAQs. So credit to the app team.
Sent from my HTC Desire X
Nice guide, first time I'm adfree, even after a reboot
did anyone get it working on desire x... mine still shows ads in apps...
I don't know, after all I'm an amateur, but the problem nightcrow described about how stuff goes back to stock after a reboot is something that happens a lot with the DX's - same thing with the bloatware. I had to remove the bloat apps from a rom.zip and flash that to avoid the problem. Seems to me there is some kind of security built in that goes beyond the norm. Otherwise I don't see why apps like Titanium work to remove apps (even after reboot) for example on most other phones, but not the DX.
Meherzad, I followed the instructions posted by nightcrow and it works for me ... try again, reboot and open an app you know normally has ads to check if it works.
Failed first time (forgot to uncheck fast boot:banghead. Reinstalled and did everything again, now works flawlesly.
ok.. working great......
nightcrow said:
Since removing ads from browser and apps was one of the main reasons to root my DX I decided to make this tutorial. Problem is you can't just install AdAway (link) and run it because after a reboot you'll have to do it again. This method is keeping the ads away even after a reboot. Remember that you'll have to update AdAway-hosts files regularly.
All credits go to Yasir Javed Ansari. I only finetuned the method he described a little bit. Because his post is somewhere in another thread it seemed right to make a tutorial for it in the themes and apps section.
First of all you'll need a properly rooted DX with superuser 3.1.3 installed. See here for a zip to install superuser and busybox or here to download a pre-rooted 1.18 stock deodexed rom with superuser and busybux installed provided by infernal77. I'm using this rom on my DX and removed a lot of bloatware with Aroma (link) right after flashing the rom. Credits go to merovig for sharing info about flashable superuser/busybox-zip and Aroma and of course to infernal77 for providing his deodexed stock rom. Although it seems that this method shouldn't be necessary when using a deodexed rom I couldn't get it to work without using the command lines, so I decided to share it anyway.
In settings - power, uncheck 'fast boot'.
Install AdAway from Play Store. Run AdAway (don't download hosts files yet) and go to settings - preferences. Check 'allow redirections' and under 'target hosts file' select '/data/data/hosts'.
Reboot to recovery and then mount /system and mount /data.
While in recovery-mode connect the device to a PC and open a command prompt.
Type:
adb shell
cd system/etc
rm hosts
ln -s /data/data/hosts hosts
Disconnect the device from PC and reboot.
Now you can run AdAway: download files and apply ad blocking.
Done!
Click to expand...
Click to collapse
have no idea how to write in command prompt
umo4u said:
have no idea how to write in command prompt
Click to expand...
Click to collapse
Windows button+R>Type cmd>enter
It doesn´t works for me...It may wont work because i have superuser v3.2?
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
nightcrow said:
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
Click to expand...
Click to collapse
you can do same in advanced-> execute command (or maybe shell - do not remember the exact naming)
adb was not working for me, too.
nightcrow said:
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
Click to expand...
Click to collapse
Why do you need ADB when you have TERMINAL in twrp. Just wondering
Anyhow, ADB will be fixed soon
Thanks for the tutorial works great with Superuser 3.2. Just to clarify something, should I leave "fast boot" mode off now?
Michael
michpan said:
Thanks for the tutorial works great with Superuser 3.2. Just to clarify something, should I leave "fast boot" mode off now?
Michael
Click to expand...
Click to collapse
I think you can turn it on.
If you'll not access recovery... when you need recovery, turn fast boot off...
Sent from my hTC branded muffin

[ROM][ROOT][STOCK][TINKER-EDITION][5.1.1] Galaxy Tab A 7.0 2016 SM-T280/T285

Samsung Galaxy Tab A 7.0 LTE/WIFI 2016 TINKER EDITION ROM (DEOXED/ROOT/XPOSED)
============================================
Update 01/04/2017
-----------------------
Tinker Edition V5.1 is now out.
* Re-added Samsung stock camera and gallery
* revert back to stock vold to fix issues people are having with micro sdcards
Now available for the SM-T285, SM-T280 to follow
Update 10/29/2016
------------------------
TWRP for the SM-T285 here
Early Build of TWRP for the T285 (see post by @ashyx will update this if an official version is released. The T280 version should be available not far behind I believe
Update 09/21/2016
-----------------------
V5 now out (root, deodexed, xposed) for the SM-T280/T285, still working on the SM-T280
Update 09/20/2016
------------------------
Turns out this device is not as locked as we all thought it too be. See thread below for my ordeal and more details:
http://forum.xda-developers.com/galaxy-tab-a/help/resources-samsung-galaxy-tab-7-0-2016-t3431022
Modifications:
===========
* Based on LMY47V.T285XXU0APCN
* Stock Boot and Recovery (Not much choice since the bootloader is locked)
* Busybox
* Hijacked Vold (using CM 12.1 sources) to run shell scripts stored in /data/scripts/vold.init
* Removed Touchwiz launcher and redundant samsung apps (Hancom office, Kidzone), replaced with Trebuchet
* Enabled r/w to the external SD Card
* Dolby Atmos mod (09/11/2016) (thanks to @Nando14sunny)
* Deodexed/Xposed (09/13/2016) (thanks to @wanam and @rovo89)
* soft linked /etc/hosts to /data/scripts/hosts and can be edited using adb shell (09/13/2016) (thanks to @venomrat)
* V5: root chainfire's SuperSu 2.78 (09/21/2016) (thanks to @Chainfire)
* stock boot animation
Special thanks also to @ashyx for initially taking a look at this device , I haven't given up on rooting this device yet.
Special thanks to @klemen241 for helping me try out the SM-T280 build
Haven't done extensive testing on Xposed modules, but the pokemon go iv mod/hacked worked and that was good enough for me (Before pokemon Go was patched). If you use this ROM feedback is highly appreciated
NOTES: To be safe, perform a cache wipe using recovery. I didn't need to do this personally but I haven't tested all use cases
NOTES: Since this rom is deodexed, the first boot will take quite a while, so please be patient .
NOTES: if you are coming from V2 and are using the mount_ext4 apps2sd scripts please update it for additional support for the V3 ROM HERE:
https://github.com/jedld/smt285_data_scripts
NOTES: (09/13/2016) Unfortunately, the V3 build fails the Google SafetyNet check, will be a problem if you play Pokemon Go
Other Notes: Removed support for zygote.init scripts in V3 as I am now using the app_process32_xposed binary, will work to get this back soon. I haven't had a need for zygote scripts though. The vold.init scripts shoud still work as before if you are using the apps2sd script
Installation Instructions:
Odin or Heimdall Required. I you are coming from the Stock Rom please wipe/factory reset to be sure. If you are upgrading from V1 or V2 you are not required to wipe unless there are problems. If you are upgrading to V3 cache wipe is recommended using recovery.
--FLASH AT YOUR OWN RISK--
1. Make sure to backup of your data and have a copy of your stock Rom in case something goes wrong.
2. Make sure your device is OEM unlocked. (Enable Developer settings and Enable the OEM unlock settings)
3. Extract ZIP file below and flash the tar.md5 file using ODIN, for details on this kindly look for instructions in the xda site.
4. For Heimdall you can use 7zip to extract the system.img from the tar.md5 and just flash the system.img itself.
Choose the appropriate download for the model (wifi only T280/ lte T285) that you have:
WIFI ONLY Download (SM-T280)
==========================
Link (V5 Deodexed, Rooted and Xposed):
https://mega.nz/#!0Jdg0a4D!XWLES1BwCPrkBlUzqNhRfRi_91LOdawYHydQ_scV2dI
Link (V3 Deodexed and Xposed - with special thanks to wanam with his custom Xposed build (86.0), and credits also to rovo89):
Download from Mega (v3 09/13/2016)
LTE Version Downloads (SM-T285)
===========================
Link (V5.1 Deodexed, Rooted and Xposed):
https://mega.nz/#!ZFFTFKYZ!NAeajNUjIgYI7zOslpWoJ2AeJ-NCKG0Ut8Buz_6eCgU
Link (V3 Deodexed and Xposed - with special thanks to wanam with his custom Xposed build (86.0), and credits also to rovo89):
Download from Mega (v3 09/13/2016)
Link (Original V2 odexed version):
Download from Mega (V2 09/11/2016)
If you have suggestions, send me a PM.
Other Notes (So people don't have to ask):
* I've tried to run superuser daemonsu, but unfortunately the sepolicy scopes for vold and zygote are too narrow in this device for supersu to use despite being root. In theory a version of daemonsu can be made specifically to run on this device with a somewhat castrated functionality though I don't have access to the source code to figure it out. Navigating the sepolicy landmine is hard.
WIFI ISSUES
=========
There are reports of wifi problems with the latest build due to wrong permissions with dhcp hooks, if so you can do the following (big thanks to @_mone):
Using adb shell:
Code:
su
mount -o rw,remount,rw /system
chmod 755 /system/etc/dhcpcd/dhcpcd-run-hooks
mount -o ro,remount,ro /system
/system is readonly by default, which is why you need the remount commands. Reboot your device after just to make sure.
Hi,
The mount_ext4_sdcard.sh script moves all apps to SD card on reboot?
Edit: did not read till the end. System apps are not move.
venomrat said:
Hi,
The mount_ext4_sdcard.sh script moves all apps to SD card on reboot?
Edit: did not read till the end. System apps are not move.
Click to expand...
Click to collapse
It won't by default for safety purposes, however you are welcome to edit the script and try to move them all
jedld said:
It won't by default for safety purposes, however you are welcome to edit the script and try to move them all
Click to expand...
Click to collapse
Thanks for your hard work. It's a pity this device is not as popular as their other models or more people would have already signed the petition.
I regret not doing more research before buying this tablet.
Hello there
At first i want to thank you for your hard work so far
Then i've got a question,
I just built this Tablet (LTE version) in my car. Now i'm on to configure it with Tasker to "act more like a car radio". It was really hard, because of the non rooted device.. But i did it so far
I used a sound mod, called Dolby Atmos (i think it's from lenovo?) on allmost every of my rooted devices to improve its sound.
I'm wondering if it would be possible that you could build in this mod inside a rom for me?
Normally i flash it as a zip file via a custom recovery so it's in the system files. but maybe you could edit it in there before the rom get flashed via odin? I could give you the zip, if u dont find it. It would be really nice!
Greetings from germany
Nando14sunny said:
Hello there
At first i want to thank you for your hard work so far
Then i've got a question,
I just built this Tablet (LTE version) in my car. Now i'm on to configure it with Tasker to "act more like a car radio". It was really hard, because of the non rooted device.. But i did it so far
I used a sound mod, called Dolby Atmos (i think it's from lenovo?) on allmost every of my rooted devices to improve its sound.
I'm wondering if it would be possible that you could build in this mod inside a rom for me?
Normally i flash it as a zip file via a custom recovery so it's in the system files. but maybe you could edit it in there before the rom get flashed via odin? I could give you the zip, if u dont find it. It would be really nice!
Greetings from germany
Click to expand...
Click to collapse
we could try, could you point me to a rom that has the specified libraries for Dolby?
Thank you, for the fast answer!
Here is the flashable zip of the Dolby Atmos, mod i used successfully on my other devices:
Mega
Greetings
Nando14sunny said:
Thank you, for the fast answer!
Here is the flashable zip of the Dolby Atmos, mod i used successfully on my other devices:
Mega
Greetings
Click to expand...
Click to collapse
Ok, wish granted, updated the ROM to include Dolby ATMOs, just redownload the ROM from the link in the main post.
jedld said:
Ok, wish granted, updated the ROM to include Dolby ATMOs, just redownload the ROM from the link in the main post.
Click to expand...
Click to collapse
Wow thank you! I'll test it right now
Edit:
It works like a charm! You really improved my devie with it!
Hi,
If it's not too troublesome, perhaps the next version can symlink the host file to a r/w folder so that ads can be blocked.
Thanks.
venomrat said:
Hi,
If it's not too troublesome, perhaps the next version can symlink the host file to a r/w folder so that ads can be blocked.
Thanks.
Click to expand...
Click to collapse
Possible, though the only r/w partition is data and cache, and it may potentially cause problems when you suddenly try to do a wipe. I'm working on deodexing and porting xposed framework for now. Either that if you've got some IP addresses that need to be blocked I can create an edition that has those entries. I'll see what I can do though there might be away to do it without breaking factory reset/wipe cache.
jedld said:
Possible, though the only r/w partition is data and cache, and it may potentially cause problems when you suddenly try to do a wipe. I'm working on deodexing and porting xposed framework for now. Either that if you've got some IP addresses that need to be blocked I can create an edition that has those entries. I'll see what I can do though there might be away to do it without breaking factory reset/wipe cache.
Click to expand...
Click to collapse
No hurry. I can wait. What you are doing now is more important. :good:
venomrat said:
No hurry. I can wait. What you are doing now is more important. :good:
Click to expand...
Click to collapse
Wish Granted. As a bonus, the latest version of the ROM is now deodexed and Xposed, please refer to the main post for the updates.
Feedback is appreciated.
How can i change the dpi?
Sent from my SM-T285 using XDA-Developers mobile app
corzradio said:
How can i change the dpi?
Sent from my SM-T285 using XDA-Developers mobile app
Click to expand...
Click to collapse
May need to modify build.prop, you may do this yourself here:
http://forum.xda-developers.com/galaxy-tab-a/how-to/guide-samsung-galaxy-tab-7-0-sm-t285-t3438296
Also there may be an Xposed framework modules that do that. Not sure though since I'm ok with the stock DPI
jedld said:
Wish Granted. As a bonus, the latest version of the ROM is now deodexed and Xposed, please refer to the main post for the updates.
Feedback is appreciated.
Click to expand...
Click to collapse
Thanks. Will need to find time to re-flash this weekend.
Regarding xposed have you actually tested any other modules that need root?
I already built a rom with xposed but it was all but useless because pretty much all the modules I use need root.
most of those I tried don't need root so far (youtube adaway, pokemon go iv). Haven't tried those that need root but I suppose those wouldn't work.
I use app settings and it works for dpi change, and you are welcome. I am glad to test stuff, its fun haha. If anyone has questions about t280 you can ask me
how can i boost the volume? since its not rooted i cant find the mixer.xml

Can someone please guide me on how to install A.R.I.S.E.?

I read the OP of A.R.I.S.E. several times, and honestly, I didn't understand it properly. And plus, I have also seen a lot of Onyx users reporting that the installation freezes in recovery. Can someone please guide me through the entire process? Thanks in advance!
meraj99 said:
I read the OP of A.R.I.S.E. several times, and honestly, I didn't understand it properly. And plus, I have also seen a lot of Onyx users reporting that the installation freezes in recovery. Can someone please guide me through the entire process? Thanks in advance!
Click to expand...
Click to collapse
I hope you are aware of flashing custom recovery and rooting your phone. Once you did that it is easy to install it.
1. Download arise from official thread. (am using magnum opus version) Make sure you download non auroma version.
2. For starters inside zip there will be a folder called our modules. Copy any of the arise_customize.prop file from that and paste it in in internal storage root directory.
3. flash the ARISE zip from recovery and you are good to go.
4. Read arise_customize.prop file for further info of adding and removing modules.
micoeyes said:
I hope you are aware of flashing custom recovery and rooting your phone. Once you did that it is easy to install it.
1. Download arise from official thread. (am using magnum opus version) Make sure you download non auroma version.
2. For starters inside zip there will be a folder called our modules. Copy any of the arise_customize.prop file from that and paste it in in internal storage root directory.
3. flash the ARISE zip from recovery and you are good to go.
4. Read arise_customize.prop file for further info of adding and removing modules.
Click to expand...
Click to collapse
which effect do you prefer?
meraj99 said:
which effect do you prefer?
Click to expand...
Click to collapse
I prefer Dolby Atmos with Dirac. Viper with ground zero preset (with my customization) nothing else. For speaker mode I use Atmos with movie preset no Viper n Dirac.

SM-A320FL - Android 7 - Root, Xposed Framwork and NO Lag Tutorial

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.

Magisk root

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/

Categories

Resources