600,000 unique entries, browse the web without distractions by using this consolidated hosts file.
Features
- Combines tons of sources including AdAway.
- Systemless so you can block ads while using Android Pay
- Looks like a small zip but the hosts file is 18mb, a couple times the size of AdAway's.
- No app required.
- Update by typing hosts in terminal, no root required.
- 600,000 unique entries.
- 4 different hosts options
- Faster blockage time by changing the redirecting to 0.0.0.0 instead of localhost like AdAway
- Four hosts options, can also be combined
1. Master = Ad & Malware block
2. Gambling = Gambling block
3. Pornography = Pornography block
4. Social = Social Media block
How to use 'hosts' terminal program
1. Type 'su' then type 'hosts'.
2. When selecting an option, you can combine multiple options into one.
3. For example, 'gps' as option would block ads, malware, gambling, pornography and social.
4. Note: The 'master' option is in all of the options so no need to include it.
5. Note: Some devices may need a reboot after updating even if ran as root.
Instructions
- Make sure you have Magisk installed.
- Download latest: v8
- Flash the zip in recovery.
- Run update if you'd like.
Credits
- @topjohnwu for Magisk
Sources
- The Adaway hosts file, updated regularly. http://www.adaway.org/hosts.txt
- MVPs.org Hosts file at http://winhelp2002.mvps.org/hosts.htm, updated monthly, or thereabouts.
- Dan Pollock at http://someonewhocares.org/hosts/ updated regularly.
- Malware Domain List at http://www.malwaredomainlist.com/, updated regularly.
- Peter Lowe at http://pgl.yoyo.org/adservers/, updated regularly.
Source (GitHub)
- github.com/RatchetPanda/ratchetpanda.github.io
Submit an issue if you'd like a entry added, changed or deleted. Pm me if you'd like contributer access.
Very cool. I'm learning up on Magisk and it looks like a fundamental shift in the development stream. It seems like AdAway was a common culprit in AP failing ( along with Chainfire's SuperSU).
SilverZero said:
Very cool. I'm learning up on Magisk and it looks like a fundamental shift in the development stream. It seems like AdAway was a common culprit in AP failing ( along with Chainfire's SuperSU).
Click to expand...
Click to collapse
Yeah I never used AdAway though, kinda pointless having another app clutter the app drawer for something that can just be flashable.
Adaway updates the hosts file every day or so, while this appears to be a static hosts file. Is this intended to replace Adaway or provide a newer/bigger hosts file for Adaway to update? If it's intended to replace Adaway, how does it get updated?
Is it possible to include a uninstallation zip, in case we decide to revert the changes?
JimSmith94 said:
Adaway updates the hosts file every day or so, while this appears to be a static hosts file. Is this intended to replace Adaway or provide a newer/bigger hosts file for Adaway to update? If it's intended to replace Adaway, how does it get updated?
Click to expand...
Click to collapse
I would need to provide an updater app, I intended to replace AdAway as this provides much more than AdAway. I'll throw together an app or something to allow updates.
njunxuan said:
Is it possible to include a uninstallation zip, in case we decide to revert the changes?
Click to expand...
Click to collapse
Sure.
RatchetPanda said:
I would need to provide an updater app, I intended to replace AdAway as this provides much more than AdAway. I'll throw together an app or something to allow updates.
Sure.
Click to expand...
Click to collapse
That would be great!!!
Adaway's hosts file is 2.01MB so this isn't magnitudes bigger...
HypoTurtle said:
Adaway's hosts file is 2.01MB so this isn't magnitudes bigger...
Click to expand...
Click to collapse
The one at adaway.org/hosts.txt is not.
RatchetPanda said:
The one at adaway.org/hosts.txt is not.
Click to expand...
Click to collapse
Adaway combines 4 sources (last I checked) into one.
Added a remover zip to the OP. :good:
Update
- Hosts is now present here: ratchetpanda.github.io/hosts.txt
Anyone can contribute and add lines.
- Combined many more sources so we are up to 3mb with 90000 unique entries.
- Located at /sdcard/hosts so you don't have to have root to edit it.
- Hosts can be updated by running hosts in terminal
If rooted type su before hosts
If not rooted a reboot is needed after updating.
- Installs Magisk if not present.
Newest is attached and I've also added it to OP.
- A small tutorial on auto updating using Tasker or another automation app.
1. Set event to whatever you want.
2. Set task to Run Shell and set the code to run to 'hosts'.
3. If you have root make sure to check the 'use root' option.
Hope you guys like it! :good:
RatchetPanda said:
Update
- Hosts is now present here: ratchetpanda.github.io/hosts.txt
Anyone can contribute and add lines.
- Combined many more sources so we are up to 3mb with 90000 unique entries.
- Located at /sdcard/hosts so you don't have to have root to edit it.
- Hosts can be updated by running hosts in terminal
If rooted type su before hosts
:
Click to expand...
Click to collapse
just flashed this on Magisk V2 on my stock 6P. seems to work great.
edit:
Went to update the hosts file via Terminal. i don't think it worked though
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
steveo17 said:
just flashed this on Magisk V2 on my stock 6P. seems to work great.
edit:
Went to update the hosts file via Terminal. i don't think it worked though
Click to expand...
Click to collapse
Can you get screenshot or log of the terminal?
RatchetPanda said:
Can you get screenshot or log of the terminal?
Click to expand...
Click to collapse
just uploaded it. in the post above
steveo17 said:
just uploaded it. in the post above
Click to expand...
Click to collapse
Hmm this is what mine looks like. Can you go to /sdcard and check to see if you have either 'hosts' or 'hosts.txt' there?
@steveo17
This should fix your issues.
Just flash in recovery, small update to correct a couple of updater bugs.
RatchetPanda said:
@steveo17
This should fix your issues.
Just flash in recovery, small update to correct a couple of updater bugs.
Click to expand...
Click to collapse
I think that worked
Although it appears to have created another hosts file
Sent from my Nexus 6P using Tapatalk
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
Update:
Unexpected side effect of flashing systemless adblock is that it seems to remove the magisk app.
Then when I flash phh supersu with the magisk app I can no longer toggle root
Sent from my Nexus 6P using Tapatalk
steveo17 said:
I think that worked
Although it appears to have created another hosts file
Sent from my Nexus 6P using Tapatalk
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
Update:
Unexpected side effect of flashing systemless adblock is that it seems to remove the magisk app.
Then when I flash phh supersu with the magisk app I can no longer toggle root
Click to expand...
Click to collapse
If you updated to Magisk v2 you need to completely remove 1 before or the app will disappear.
RatchetPanda said:
If you updated to Magisk v2 you need to completely remove 1 before or the app will disappear.
Click to expand...
Click to collapse
remove v1 of magisk or this adblock?
Related
THIS POST IS CLOSED, IT MOVED!
HERE
Thanks goes to: fi01 for finding the bug, Jcase for making the exploit, Moronig for modifying the exploit, slayer615 for making the original batch bundle.
Help please http://forum.xda-developers.com/showpost.php?p=47883338&postcount=41
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EniGmA1987 said:
http://forum.xda-developers.com/showpost.php?p=47883338&postcount=41
Click to expand...
Click to collapse
I have root. I'm on version 13.3.1.0 on my 7" HDX. If you follow the tutorial it should work. (It did for me) What version are you running?
Says 13.3.0.2_user_302075320. Installed on Monday Jul, 29th, 2013 5:01 PM
Just got the tablet today and have not updated anything at all. My tablet cant check for updates since before I turned it on I blacklisted the IP addresses from my router that Amazon uses to push updates to Kindles
Hurry, update to 13.3.1.0 before a newer update comes (or download the update here and for directions to manually install the update). Don't blacklist those IP's until you root it. Update first.
Once you get root you can configure iptables on the tablet to blacklist it but im testing this. I got root 2 hours ago. Once I get it working I'll post a tut.
But you need to be on version 13.3.1.0
Alright I am downloading it now on the tablet, but it seems to be taking a while so I doubt I will get a chance to try for root again tonight.
EniGmA1987 said:
Alright I am downloading it now on the tablet, but it seems to be taking a while so I doubt I will get a chance to try for root again tonight.
Click to expand...
Click to collapse
That's fine. It's a over 700mb. I will be downloading it too, for a backup if Amazon decides to take it down. Good luck!
Faznx92 said:
1: Download Minimal ADB and Fastboot and install it. here
2: Get the adb drivers and install. here
3: Download latest Busybox to your HDX and install it. (It will not run untill you have root, this is for later.)(I got it from 1mobile market here)
4: Download jcase/fi01 code here
5: Download Moronig redone code http://goo.gl/4gBmq5
6: Enable adb on the Kindle
7: Connect Kindle to computer
8: Goto Device Manager in Control Panel
9: Look for the unsupported adb device (if not found safely remove hardware the kindle on the taskbar)
10: Click the unsupported device and click update driver then point it to the android_winusb file in the driver install directory
11: Unpack the files, rename Moroning's file to exploit and copy to the Minimal ADB and Fastboot install base directory, copy jcase's code EXCEPT the exploit file there as well.
12: Run Minimal ADB and Fastboot, make sure your device is connect first
Code:
adb devices
If not listed go back to step 6
13: Copy and paste this into the cmd prompt. Ignore if it says it fails
Code:
adb push su /data/local/tmp/
adb push rootme.sh /data/local/tmp/
adb push exploit /data/local/tmp/
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell chmod 755 /data/local/tmp/exploit
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
At this point you should be rooted. You can now finish installing Busybox on your HDX. To check if you have root if your unsure type
Code:
adb shell
then type
Code:
su
If not, reply. Remember this is tested to work on my Kindle Fire HDX 7" 13.3.1.0
Notes:
If the Hdx is updated past this point Amazon may patch the exploit and so you loose root.
We need to start a thread on how to stop/block Amazon from pushing updates to the HDX.
Click to expand...
Click to collapse
Do we need a Superuser app installed after root is gained like SuperSu. Also is it possible to unroot using SuperSu script in the settings.
Android Cowboy said:
Do we need a Superuser app installed after root is gained like SuperSu. Also is it possible to unroot using SuperSu script in the settings.
Click to expand...
Click to collapse
Never tried it yet, but you should. You have full root access.
Faznx92 said:
Never tried it yet, but you should. You have full root access.
Click to expand...
Click to collapse
Have confirmed that SuperSu does work and it will also unroot using the option in the settings.
Android Cowboy said:
Have confirmed that SuperSu does work and it will also unroot using the option in the settings.
Click to expand...
Click to collapse
Yes sir. SuperSU is working. Spread the word lol. I got to get some shut eye. I downloaded supersu from 1mobile market.
Someone got the playstore to work?
Gesendet von meinem Nexus 4 mit Tapatalk
Android Cowboy said:
Do we need a Superuser app installed after root is gained like SuperSu. Also is it possible to unroot using SuperSu script in the settings.
Click to expand...
Click to collapse
If you don't install a superuser app, root will still work, but any app that requests it, gets it, and no notification.
Supersu works with that binary, but you can install superuser and let it update the su binary and it will work as well.
---------- Post added at 09:08 AM ---------- Previous post was at 09:04 AM ----------
cebulank said:
Someone got the playstore to work?
Gesendet von meinem Nexus 4 mit Tapatalk
Click to expand...
Click to collapse
Some people are claiming to have it working, but they won't share how they did it...
Moronig said:
If you don't install a superuser app, root will still work, but any app that requests it, gets it, and no notification.
Supersu works with that binary, but you can install superuser and let it update the su binary and it will work as well.
---------- Post added at 09:08 AM ---------- Previous post was at 09:04 AM ----------
Some people are claiming to have it working, but they won't share how they did it...
Click to expand...
Click to collapse
SuperSU works, busybox works, I got root, I will be running test soon.
-update Play store does not work
Google play services works
Can this tutorial be used to root the Kindle Fire HDX 8.9 too?
lanegan said:
Can this tutorial be used to root the Kindle Fire HDX 8.9 too?
Click to expand...
Click to collapse
I'm posting that soon(to this thread). I do not have one so I can't confirm it works. Check back here shortly.
-Update I have it posted on the main thread.
Questions about Amazon updates
Has anyone tried to see if you can block the OTA updates like the kindle fire hd.
Using ES File Explorer app, navigate to the /system/etc/security folder. Rename or move the otacerts.zip file.
-credit goes to androidcowboy
Thanks For the Root it works Great
fr09n said:
Has anyone tried to see if you can block the OTA updates like the kindle fire hd.
Using ES File Explorer app, navigate to the /system/etc/security folder. Rename or move the otacerts.zip file.
-credit goes to androidcowboy
Thanks For the Root it works Great
Click to expand...
Click to collapse
I'll try it out.
-UPDATE- I can't confirm if it works or not. Someone else needs to try this up to see if it stops updates.
I'm running iptables.
This worked for me once I updated to 13.3.1. Guess the bug is either not present in the older kernel or it is at a different memory address.
EniGmA1987 said:
This worked for me once I updated to 13.3.1. Guess the bug is either not present in the older kernel or it is at a different memory address.
Click to expand...
Click to collapse
Yah. I think that's what lead someone to port the 8.9" 14.3.1 hdx exploit to 7" 13.3.1
Guide: Getting Xposed RunningThis morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
What you'll need:
A paid copy of Mofo (obviously)
Either a modified system image containing Xposed already, or if you like, you can modify one yourself as described in this tutorial. I've already created a modified system image to include Xposed as well as Wifi Tethering and a modified hosts file for ad blocking.
The Xposed Installer apk
Xposed Installer needs to be installed on your phone
Terminal Emulator and ES File Explorer from the play store need to be installed on your phone
A rooted image flashed to your phone
Before flashing anything, this is what you need to do:
On your computer, find your de.robv.android.xposed.installer_v33_36570c.apk and rename it to be a .zip file.
Open this .zip file and extract /assets/XposedBridge.jar and, if you're modifying your own system image, extract /assets/arm/app_process_xposed_sdk16 as well.
Put XposedBridge.jar somewhere on your phone, I like to use the Downloads folder so I don't lose track of it later.
In ES File Explorer, navigate to /data (NOT SDCARD/DATA)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure it doesn't say sdcard > data!
Create a folder called "xposed"
Long press the folder, select properties, and set permissions to 755
Set the owner of the folder to root and the group to shell
Move XposedBridge.jar into the xposed folder we just created.
Make the permissions of XposedBridge.jar 644
As before, make the owner root and the group shell.
Open the Xposed Installer app on your phone.
Open terminal emulator and type
Code:
ps | grep xposed
This will return a pattern like the following. Make a note of the first seven characters, as shown (the first is a lowercase u)
Return to /data/xposed
Create two new files: modules.list and modules.whitelist
Make the permissions on both files 644 as above
Set the owner to the seven characters we noted down earlier and the group to shell on both files
If you're flashing a pre-compiled image with Xposed, you're done here! Go ahead and flash, and enjoy!
If you're modifying your own system image, you've got some more work to do. Take app_process_xposed_sdk16 from the Xposed apk and rename it to app_process.
In your turbo system image, navigate to /bin/ and replace app_process with the one from Xposed Framework. Make sure its permissions are set to 755:
Code:
sudo chmod 755 /path/to/img/bin/app_process
Linux does not allow setting the group of a file to a nonexistent group, so on your pc you'll have to make a shell group:
Code:
sudo groupadd shell
Change the group of app_process to shell:
Code:
sudo chgrp shell /path/to/img/bin/app_process
You're ready to flash!
NOTE: If XposedBridge.jar reports problems, try setting installation mode in the Xposed installer app to recovery (flash manually) and hitting install, then reboot.
You're done! Xposed should show up as installed! Don't use any modules that require system write access, such as replacing system icons, but most modules (ie GravityBox) work fine without it.
Ekkoria said:
This morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
Click to expand...
Click to collapse
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
ntxct said:
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
Click to expand...
Click to collapse
Same here! When I finally opened Xposed Installer and saw it read the framework as installed, I've almost never been so excited about something Android.
i dont need it but its a great guide, easy, short and with pictures!
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Thanks so much man, about to flash. Will let you know how it goes.
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
It did not work for xposedbridge.jar
aven1357 said:
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Click to expand...
Click to collapse
Yes, you will need to be rooted first to perform these actions. Apologies for not originally including this. OP updated
savagebunny said:
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
Click to expand...
Click to collapse
Yes please do so. I'd be very interested.
Sent from my XT1254 using XDA Free mobile app
I am having trouble with es file explr it tells me the operation failed when trying to do anything I have root and I enabled root for ES it seemed to work on root browser fine (I reset my device and just installed es so far)
edit checked and the root enhancement options are greyed out?
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
I am having same problem as u smokie
smokie75 said:
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
Click to expand...
Click to collapse
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
Thanks! That worked!
Thanks for this , works great , now we just need one with busybox preinstalled
Stuck at this point any help?[/ATTACH]
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
so will doing this enable gravitybox to work on the turbo?
hmltnjrmy7 said:
Stuck at this point any help?[/ATTACH]
Click to expand...
Click to collapse
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
rayjr13 said:
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
Click to expand...
Click to collapse
Lol the dead droid freaked me out at first, but I'm so happy xposed finally works!!!
What you will need:
To be on Lollipop WITH root (go here if you need to flash the rooted ROM)
BusyBox to be installed (it should already be installed on the rooted ROM, if not then search the Play Store or use your favorite one)
A copy of Viper4Android v2.3.4.0 (Download from here)
A file browser that can access the /system partition and change permissions (I prefer ES File Explorer but you can use whatever you like)
Titanium Backup (or you can use the application manager in the Settings app)
Firstly, what you will need to do is use your file browser and create a folder called "Viper4Android" in your /system/priv-app/ folder. Set the permission for this folder to rwxr-xr-x or 0755, then paste your Viper4Android APK into the folder you created and set the permission for the APK to rwxrwxrwx or 0777, with root being owner and group for both folder and APK.
Secondly, what you will need to do is browse to /system/etc/ with your file browser and open the file init.qcom.post_boot.sh and at the very bottom of the file paste this:
Code:
/system/xbin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
It is imperative that you make sure you are using Unix line endings instead of anything else.
Thirdly, use Titanium Backup or the Application Manager to freeze SoundAlive, as all music apps will attempt to default to it. Also you may want to freeze the Adapt Sound app, as if you enable it will then be used over V4A.
Lastly, reboot your phone and then install the drivers and reboot one last time. I can confirm that it works on Play Music, and that it doesn't work on the stock Music player (however I believe there is a way to get it to work somewhere on the internet).
Problems:
Viper4Android fails at installing!
Click to expand...
Click to collapse
You are to create it as a system app, so follow the first step.
Viper4Android doesn't appear!
Click to expand...
Click to collapse
Make sure you followed the first step correctly and set the proper permissions.
Viper4Android still says Abnormal and Unsupported in the status!
Click to expand...
Click to collapse
Make sure you pasted the command into the init.qcom.post_boot.sh file and that you used Unix line endings, as using DOS or Mac line endings add extra characters that Android will try to parse as actual text.
Viper4Android says that BusyBox isn't installed!
Click to expand...
Click to collapse
This bug happens sometimes, I found the best way to beat it is to open your BusyBox app and just put it in the background and try the driver installation again.
I enabled everything and my music still sounds the same!
Click to expand...
Click to collapse
Make sure you freeze SoundAlive and Adapt Sound, as they will be used before Viper4Android, also you may need to put V4A into Compatibility mode to use with certain music players. Also you can't use the stock Music player (but I think there is a way somewhere on the internet).
My phone broke and won't boot!
Click to expand...
Click to collapse
Then you may want to wait until a recovery flashable zip is made, but at no point are the steps going to brick your phone, you can just boot to Safestrap or flash back.
Notes:
This process can probably be done very easily with a init.d script and a recovery flashable zip, but I currently don't have the time and don't want to risk screwing up someone's phone.
You can use any other Viper4Android mod, as long as it is v2.3.4.0, I prefer this version which looks very nice. You can extract the file from the zip attachment and just follow the steps here.
You do not need to have SELinux set to permissive, as even with using MultiSystem to set it to permissive, it still didn't work until the above command is used.
I haven't tested whether effects like convolver or DDC work, but they should.
Thanks to:
@ihancioglu for the code that allows it to work
@nappent for most of the steps needed to get it running
EXTRA:
Here is an init.d script that will do the bypass for you, however, you must have init.d support. As it stands right now, Walter.White's Lollipop ROM does not have init.d, if you want to enable init.d, you have to add
Code:
/system/etc/init.d/*
to the end of init.qcom.post_boot.sh and create an init.d folder in /system/etc.
Script: https://mega.nz/#!ZpIUCbrb!QONi8bWb1afE47_JnwxgpBcXoKFuPG3mpnyFX4r83G0
What process did you use to be able to write to the root. I can not gain root access even though i have su, busybox, and several other apps with root access. I have tried using ES File explorer with no success. It will not access the root of the device.
---------- Post added at 09:31 PM ---------- Previous post was at 08:35 PM ----------
100% verified and working. Big thanks!!!
Works perfectly. Thanks for this work around OP!
Any thoughts on using NuPlayer vs. AwesomePlayer in dev. options?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
joshuaburnsjr said:
What process did you use to be able to write to the root. I can not gain root access even though i have su, busybox, and several other apps with root access. I have tried using ES File explorer with no success. It will not access the root of the device.
---------- Post added at 09:31 PM ---------- Previous post was at 08:35 PM ----------
100% verified and working. Big thanks!!!
Click to expand...
Click to collapse
Root Browser worked for me.
KTownGT said:
Any thoughts on using NuPlayer vs. AwesomePlayer in dev. options?.
Click to expand...
Click to collapse
I use NuPlayer, but to be honest I haven't seen or heard of any difference. Some guides say that disabling NuPlayer will allow V4A to work, but V4A has worked just perfectly fine with NuPlayer enabled.
Among other things, creating a recovery flashable zip has fallen through. I have come across a problem where I can't modify init.qcom.post_boot.sh from a recovery, be it SafeStrap or FlashFire. I have also discovered something else, init.d support was supposed to be included with Walter.White's Lollipop ROM, but his script encountered the same problem as me, it couldn't append to init.qcom.post_boot.sh. So right now anyone using his ROM does not have init.d setup, luckily, it can be very easily enabled. All you have to do is add
Code:
/system/etc/init.d/*
to the end of init.qcom.post_boot.sh and create an init.d folder in /system/etc and you are good to go. I have attached an init.d script to the main post that can make use of init.d and do the bypass.
Namelesswonder said:
I use NuPlayer, but to be honest I haven't seen or heard of any difference. Some guides say that disabling NuPlayer will allow V4A to work, but V4A has worked just perfectly fine with NuPlayer enabled.
Click to expand...
Click to collapse
Exactly why I asked... lol
Looks like it is only required when setting SELinux to permissive; which doesn't appear to be required. You literally saved me from going back to 4.4.2, just for V4A btw:good:
Namelesswonder said:
Among other things, creating a recovery flashable zip has fallen through. I have come across a problem where I can't modify init.qcom.post_boot.sh from a recovery, be it SafeStrap or FlashFire. I have also discovered something else, init.d support was supposed to be included with Walter.White's Lollipop ROM, but his script encountered the same problem as me, it couldn't append to init.qcom.post_boot.sh. So right now anyone using his ROM does not have init.d setup, luckily, it can be very easily enabled. All you have to do is add
Code:
/system/etc/init.d*
to the end of init.qcom.post_boot.sh and create an init.d folder in /system/etc and you are good to go. I have attached an init.d script to the main post that can make use of init.d and do the bypass.
Click to expand...
Click to collapse
Answers my second question about init.d. :good:
Have been debating whether to stay on Alliance or go back to OTA, seeing as how I don't use the customization settings & need NFC
KTownGT said:
Exactly why I asked... lol
Looks like it is only required when setting SELinux to permissive; which doesn't appear to be required. You literally saved me from going back to 4.4.2, just for V4A btw:good:
Answers my second question about init.d. :good:
Have been debating whether to stay on Alliance or go back to OTA, seeing as how I don't use the customization settings & need NFC
Click to expand...
Click to collapse
I originally stayed off of Lollipop for a month because I couldn't get V4A to work, but I tried to find a solution after people got it working on the Galaxy S6.
I made this guide because using MultiSystem to set SELinux to permissive did not fix the issue. It was like the policies for SELinux were still being enforced. Also, I made a mistake for the init.d code, it should be
Code:
/system/etc/init.d/*
. Currently stock rooted Lollipop is ok, with Xposed now working and Wanam just recently updated you can make stock usable now.
Namelesswonder said:
I originally stayed off of Lollipop for a month because I couldn't get V4A to work, but I tried to find a solution after people got it working on the Galaxy S6.
I made this guide because using MultiSystem to set SELinux to permissive did not fix the issue. It was like the policies for SELinux were still being enforced. Also, I made a mistake for the init.d code, it should be
Code:
/system/etc/init.d/*
. Currently stock rooted Lollipop is ok, with Xposed now working and Wanam just recently updated you can make stock usable now.
Click to expand...
Click to collapse
Same pretty much. It's painful going from using V4A & a USBDAC to straight LP.
working perfectly.. thanks
Works amazing jus one question the download from mediafire has two different apps both the same version which should I have installed
Works for me! Thanks.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Orion.Lamas said:
Works amazing jus one question the download from mediafire has two different apps both the same version which should I have installed
Click to expand...
Click to collapse
On V4A's website?
There should be an APK for before JB, and one for KK/LP. You should use the one that's like"V4A_FX_4.x.apk"
Sent from my iPad using Tapatalk
Thanks OP! Got it all working and the sound quality has definitely improved. Question though, in past versions I loved adjusting the IRSamples. Is that no longer a thing in this latest version?
Viper4android worked again!
Namelesswonder said:
What you will need:
To be on Lollipop WITH root (go here if you need to flash the rooted ROM)
BusyBox to be installed (it should already be installed on the rooted ROM, if not then search the Play Store or use your favorite one)
A copy of Viper4Android v2.3.4.0 (Download from here)
A file browser that can access the /system partition and change permissions (I prefer ES File Explorer but you can use whatever you like)
Titanium Backup (or you can use the application manager in the Settings app)
Firstly, what you will need to do is use your file browser and create a folder called "Viper4Android" in your /system/priv-app/ folder. Set the permission for this folder to rwxr-xr-x or 0755, then paste your Viper4Android APK into the folder you created and set the permission for the APK to rwxrwxrwx or 0777, with root being owner and group for both folder and APK.
Secondly, what you will need to do is browse to /system/etc/ with your file browser and open the file init.qcom.post_boot.sh and at the very bottom of the file paste this:
Code:
/system/xbin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
It is imperative that you make sure you are using Unix line endings instead of anything else.
Thirdly, use Titanium Backup or the Application Manager to freeze SoundAlive, as all music apps will attempt to default to it. Also you may want to freeze the Adapt Sound app, as if you enable it will then be used over V4A.
Lastly, reboot your phone and then install the drivers and reboot one last time. I can confirm that it works on Play Music, and that it doesn't work on the stock Music player (however I believe there is a way to get it to work somewhere on the internet).
Problems:
You are to create it as a system app, so follow the first step.
Make sure you followed the first step correctly and set the proper permissions.
Make sure you pasted the command into the init.qcom.post_boot.sh file and that you used Unix line endings, as using DOS or Mac line endings add extra characters that Android will try to parse as actual text.
This bug happens sometimes, I found the best way to beat it is to open your BusyBox app and just put it in the background and try the driver installation again.
Make sure you freeze SoundAlive and Adapt Sound, as they will be used before Viper4Android, also you may need to put V4A into Compatibility mode to use with certain music players. Also you can't use the stock Music player (but I think there is a way somewhere on the internet).
Then you may want to wait until a recovery flashable zip is made, but at no point are the steps going to brick your phone, you can just boot to Safestrap or flash back.
Notes:
This process can probably be done very easily with a init.d script and a recovery flashable zip, but I currently don't have the time and don't want to risk screwing up someone's phone.
You can use any other Viper4Android mod, as long as it is v2.3.4.0, I prefer this version which looks very nice. You can extract the file from the zip attachment and just follow the steps here.
You do not need to have SELinux set to permissive, as even with using MultiSystem to set it to permissive, it still didn't work until the above command is used.
I haven't tested whether effects like convolver or DDC work, but they should.
Thanks to:
@ihancioglu for the code that allows it to work
@nappent for most of the steps needed to get it running
EXTRA:
Here is an init.d script that will do the bypass for you, however, you must have init.d support. As it stands right now, Walter.White's Lollipop ROM does not have init.d, if you want to enable init.d, you have to add
Code:
/system/etc/init.d/*
to the end of init.qcom.post_boot.sh and create an init.d folder in /system/etc.
Script: https://mega.nz/#!ZpIUCbrb!QONi8bWb1afE47_JnwxgpBcXoKFuPG3mpnyFX4r83G0
Click to expand...
Click to collapse
I used link2sd to covert music & video players from system to user apps & viper4android worked greatly!
SilverStone641 said:
Thanks OP! Got it all working and the sound quality has definitely improved. Question though, in past versions I loved adjusting the IRSamples. Is that no longer a thing in this latest version?
Click to expand...
Click to collapse
Working here. Did you change the UI setting?
Sent from my SAMSUNG-SM-N900A using Tapatalk
hllah66 said:
I used link2sd to covert music & video players from system to user apps & viper4android worked greatly!
Click to expand...
Click to collapse
Good to know that is what you have to do to get V4A working on stock Music and Video Player. I don't know if that would bring up any issue, but nice find.
Works like a charm on AllianceROM Lollipop v9.1 Extreme Customisation 05.24.2015 :victory:
KTownGT said:
Working here. Did you change the UI setting?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Interesting. I don't have that option at all in my interface. I haven't adjusted any UI settings either. Is there another component that needs installing?
SilverStone641 said:
Interesting. I don't have that option at all in my interface. I haven't adjusted any UI settings either. Is there another component that needs installing?
Click to expand...
Click to collapse
Open V4A --> tap settings --> tap "UI Settings" --> Tap "Expert". Should have it after that
KTownGT said:
Open V4A --> tap settings --> tap "UI Settings" --> Tap "Expert". Should have it after that
Click to expand...
Click to collapse
MY HERO!! Thank you so much!! I've got all my favorite settings options back plus it sounds even better! Thank you!!
Namelesswonder said:
Good to know that is what you have to do to get V4A working on stock Music and Video Player. I don't know if that would bring up any issue, but nice find.
Click to expand...
Click to collapse
Hello...
How is that accomplished?
They can be detailed the activities necessary to achieve this?
Thanks!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
I noticed that old init.d enabling methodes aren't working anymore with latest firmwares on the Xperia Z5
I tried many of available traditional methodes (that relies on init.qcom.post_boot.sh, install-recovery.sh ... I believe they stopped working because a lot of them used SuperSU ), also tried many magisk init.d emulators but none of them worked as well. My mod uses simpler and modern method I thought I'd share it with you to help those who still have troubles activating init.d especially newbies
What is init.d ?
Init.d plays an important role in the world of Android development and customization It allows users to install scripts and mods to be run at boot—everything from battery tweaks to performance tweaks..
Click to expand...
Click to collapse
Compability
Code:
- Any device
- Tested with Magisk v14 but should work on all V12+
Bugs
Code:
- You tell me
Downloads
Second post
Credits
@topjohnwu for making this possible
RXSMB Team
Version Information
Status: Stable
Current Stable Version: 2.2
Stable Release Date: 2017-09-27
Created 2017-09-23
Last Updated 2017-07-29
[MOD][Magisk][Universal] A simple init.d enabler (system-less) [Fixed*]
Downloads
Please use remover before updating to new versions
Make sure you read the notes above carefully before downloading !
Magisk 14+
https://www.androidfilehost.com/?fid=962021903579480972
Magisk 15+
https://drive.google.com/open?id=1bzT5Uu2jIZDJpcaBvSMYqF11M-YYz5SJ
Remover UPDATED 27.09.2017
https://www.androidfilehost.com/?fid=889964283620753913
How to make sure it's working ?
Code:
- Go to [B]/data/[/B] if you find the file [B]"initd_test.log" then congrats it's working [/B]
Changelog
Code:
2.2 | 29/09/2017
- Bug fixes for some devices
2.1 | 27/09/2017
- Removed sleep for 30 sec post boot (to avoid conflicts with some scripts)
2.0 | 24/09/2017
- Changed permissions from 777 to 755 (standard)
- Added writing permissions to init.d folder too
1.0 | 23/09/2017
- First release
DO NOT STEAL MY WORK!!
FEEL FREE TO USE MY MOD IN YOUR ROM, JUST GIVE PROPER CREDITS !
Flashed buh phone stuck at bootlogo, had to flash uninstaller zip before phone boots up.....
Flashed the mod in Magisk and rebooted, the mod made the fingerprint option unavailable in Settings. (stock 7.1.1 140)
Disabled the mod Magisk and rebooted, fingerprint appeared again.
Can you look into it?
P/s: flash the mod directly in TWRP will get you stuck at boot logo.
whalesplaho said:
Flashed buh phone stuck at bootlogo, had to flash uninstaller zip before phone boots up.....
Click to expand...
Click to collapse
colorado48 said:
Flashed the mod in Magisk and rebooted, the mod made the fingerprint option unavailable in Settings. (stock 7.1.1 140)
Disabled the mod Magisk and rebooted, fingerprint appeared again.
Can you look into it?
P/s: flash the mod directly in TWRP will get you stuck at boot logo.
Click to expand...
Click to collapse
Please update to new fixed version I updated the link now for second time nothing hardcoded it's working perfectly for me on 32.4.A.0.160 should do same for all roms/devices
Do not forget to use remover before updating .. enjoy
New version works now ?
Fingerprint works now too.
I still dnt have tha log file.... But test file inside init.d folder!!
Woooooooppppppssss......
colorado48 said:
New version works now
Fingerprint works now too.
Click to expand...
Click to collapse
good bro enjoy
whalesplaho said:
I still dnt have tha log file.... But test file inside init.d folder!!
Woooooooppppppssss......
Click to expand...
Click to collapse
how is that, what kernel/rom you are using.. working fine on stock here
Also note that you might need to wait 30sec at least after boot before init.d takes effect
So try to refresh in your file manager and check the result in /data/
korom42 said:
good bro enjoy
how is that, what kernel/rom you are using.. working fine on stock here
Also note that you might need to wait 30sec at least after boot before init.d takes effect
So try to refresh in your file manager and check the result in /data/
Click to expand...
Click to collapse
Im on crdroid lineage os and using stock kernel too brov.. 30secs? Okay will try again.
New version is up ! .. minor changes but better update
2.1 | 27/09/2017
Code:
- Removed sleep for 30 sec post boot (to avoid conflicts with some scripts)
Bro @korom42 there is no initd_test.log in the data folder on my XZ
Verstuurd vanaf mijn F8331 met Tapatalk
This works but breaks both safetynet checks for me on a Z3C LOS 14.1 with Universal safetynet fix 10.1.
@korom42, first of all, thanks for this awesome work. I can confirm that this mod is working on Xperia Z5 Premium E6833, 7.1.1 stock rom with magisk 14.2 beta.
BUGS:
1) the test file present in the /system/etc/init.d namely "00test" is undeleteable. I tried remounting the system as R/W but still get the message "Device or Resource Busy".
2) When I create my own scripts (which is just another test script or any other) in the /system/etc/init.d folder, it gets saved successfully with permissions rwx-r-x-r-x. But when i restart the device, my created scripts get deleted automatically without execution.
Is their something I'm doing wrong???
P.S: I have attached the script I'm using for your consideration....
Regards
Adil
@korom42, i figured out the problem.
EVERYONE FACING PROBLEMS WITH THIS MODULE SHOULD PLACE THIER SCRIPTS IN THE FOLLOWING PATH:
/magisk/simple_initd/system/etc/init.d
DON'T PLACE THE SCRIPTS IN:
/system/etc/init.d
This is a systemless module, placing files in the latter mentioned path you modify the system which kind of ruins the systemless purpose....
Thanks alot for this extremely awesome module @korom42
Regards
Adil
Adil Tariq said:
[MENTION=5033594]
This is a systemless module, placing files in the latter mentioned path you modify the system which kind of ruins the systemless purpose....
Click to expand...
Click to collapse
However the module breaks safetynet immediately after installing. Is it because of the test output file created in /data or otherwise?
I'm using this init.d link module instead now with a small mod and workaround. I've written my experiences in that thread. It's not straightforward but it's the only semi-working safetynet init.d for me.
Adil Tariq said:
@korom42, first of all, thanks for this awesome work. I can confirm that this mod is working on Xperia Z5 Premium E6833, 7.1.1 stock rom with magisk 14.2 beta.
BUGS:
1) the test file present in the /system/etc/init.d namely "00test" is undeleteable. I tried remounting the system as R/W but still get the message "Device or Resource Busy".
2) When I create my own scripts (which is just another test script or any other) in the /system/etc/init.d folder, it gets saved successfully with permissions rwx-r-x-r-x. But when i restart the device, my created scripts get deleted automatically without execution.
Is their something I'm doing wrong???
P.S: I have attached the script I'm using for your consideration....
Regards
Adil
Click to expand...
Click to collapse
Adil Tariq said:
@korom42, i figured out the problem.
EVERYONE FACING PROBLEMS WITH THIS MODULE SHOULD PLACE THIER SCRIPTS IN THE FOLLOWING PATH:
/magisk/simple_initd/system/etc/init.d
DON'T PLACE THE SCRIPTS IN:
/system/etc/init.d
This is a systemless module, placing files in the latter mentioned path you modify the system which kind of ruins the systemless purpose....
Thanks alot for this extremely awesome module @korom42
Regards
Adil
Click to expand...
Click to collapse
Alright, if you managed to use the mod while keeping SafetyNet bypass working than that's great
but I won't change anything since it's not a reliable way because the user will have to move his files each time adding new scripts
- for deleting the 00test file did you try a different file manager .. root browser works fine here
Infy_AsiX said:
However the module breaks safetynet immediately after installing. Is it because of the test output file created in /data or otherwise?
I'm using this init.d link module instead now with a small mod and workaround. I've written my experiences in that thread. It's not straightforward but it's the only semi-working safetynet init.d for me.
Click to expand...
Click to collapse
- Just disable the module from Magisk Manager whenever you need SafetyNet bypass back .. will try to make it SafetyNet compatible in next versions if possible
@korom42 i just want to report that safety is now also broken on my Xperia Z5 Premium E6833 Stock Rom (LOL) after just 2 reboots. Uninstalling this module fixes the issue. Hope you will find a way to make this module work with safetynet....
@Infy_AsiX @Adil Tariq @crisout
This is a quick temporary fix for SafetyNet untill I release I new version .. thanks to @Mondor1979
As for safety net, there is the very easy way to fix it. Just reinstall busybox version 27.2 after each reboot that will return safetynet back to pass state. I use meefik and that helps.
Click to expand...
Click to collapse
Download the app here
Altenative by Stephen (Stericson)
korom42 said:
@Infy_AsiX @Adil Tariq @crisout
This is a quick temporary fix for SafetyNet untill I release I new version .. thanks to @Mondor1979
Download the app here
Altenative by Stephen (Stericson)
Click to expand...
Click to collapse
Great! it's working!
Thanks!
korom42 said:
@Infy_AsiX @Adil Tariq @crisout
This is a quick temporary fix for SafetyNet untill I release I new version .. thanks to @Mondor1979
Download the app here
Altenative by Stephen (Stericson)
Click to expand...
Click to collapse
crisout said:
Great! it's working!
Thanks!
Click to expand...
Click to collapse
Did you find out another fix to safetynet? It's not working anymore
1. Install arter kernel & Magisk
2. Remove /vendor/overlay/RazerAuraBluetoothRes.apk using your favorite explorer - This overlay disables APTX
3. Open /vendor/build.prop using your favorite explorer and search "persist.vendor.bt.a2dp_offload_cap=sbc" and delete line.
After that, add quote to bottom line. and Save.
#
# Addon
#
persist.vendor.btstack.enable.twsplus=true
# This is not from code.
persist.vendor.btstack.connect.peer_earbud=true
persist.vendor.btstack.enable.splita2dp=true
persist.vendor.service.bt.bca=true
persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptxtws-aptxhd-aac-ldac
Click to expand...
Click to collapse
4. Install "APTX for Android Ore & Pie" from magisk manager (slide left to right -> Downloads -> Search -> Install) and reboot
5. PROFIT :fingers-crossed:
This also enables APTX-TWS (Qualcomm TWS Plus) but I didn't test it because I have no device.
Holy sh*t, that really works! I've been searching for a solution to that for such a looong time...
Btw, I took the "APTX for Android Ore & Pie"-Module and added your props to the system.prop inside of that module and then I added an empty dummy of RazerAuraBluetoothRes.apk into the (has to be created) folder /vendor/overlay/ inside of the module's /system folder. That way it is systemless and therefore doesn't make any problems regarding AVB, safetynet and whatnotelse
Thank you so much OP and The Brad. Your method and Brad's systemless is the best combo. In android 9 we don't have AAC, anyway to add those libraries as well?
Does this whole process need rooting? (i'm very new to android space and don't know much about its advantages & disadvantages. Staying away for now since it's just a week old phone.)
the_brad said:
Holy sh*t, that really works! I've been searching for a solution to that for such a looong time...
Btw, I took the "APTX for Android Ore & Pie"-Module and added your props to the system.prop inside of that module and then I added an empty dummy of RazerAuraBluetoothRes.apk into the (has to be created) folder /vendor/overlay/ inside of the module's /system folder. That way it is systemless and therefore doesn't make any problems regarding AVB, safetynet and whatnotelse
Click to expand...
Click to collapse
How was the dummy apk created?
On the phone by using solid explorer (every other file explorer should do as well). I create a new file an name it RazerAuraBluetoothRes.apk and that's it. I would attach it here but obviously apk and zip files are not allowed.
Gesendet von meinem Phone 2 mit Tapatalk
the_brad said:
On the phone by using solid explorer (every other file explorer should do as well). I create a new file an name it RazerAuraBluetoothRes.apk and that's it. I would attach it here but obviously apk and zip files are not allowed.
Gesendet von meinem Phone 2 mit Tapatalk
Click to expand...
Click to collapse
Did you delete this line also ?persist.vendor.bt.a2dp_offload_cap=sbc
Nope, because you add it in the system.prop and magisk then overwrites any existing props.
Gesendet von meinem Phone 2 mit Tapatalk
the_brad said:
Holy sh*t, that really works! I've been searching for a solution to that for such a looong time...
Btw, I took the "APTX for Android Ore & Pie"-Module and added your props to the system.prop inside of that module and then I added an empty dummy of RazerAuraBluetoothRes.apk into the (has to be created) folder /vendor/overlay/ inside of the module's /system folder. That way it is systemless and therefore doesn't make any problems regarding AVB, safetynet and whatnotelse
Click to expand...
Click to collapse
Hey Brad! Does this whole process need rooting? (i'm very new to android space and don't know much about its advantages & disadvantages. Staying away for now since it's just a week old phone.)
shahriyarali said:
Hey Brad! Does this whole process need rooting? (i'm very new to android space and don't know much about its advantages & disadvantages. Staying away for now since it's just a week old phone.)
Click to expand...
Click to collapse
Yes, it needs rooting which includes unlocking your bootloader (which deletes all your data on your phone!!!) and installing magisk. If you don't know much about that process, you better read some basic tutorials first
the_brad said:
Yes, it needs rooting which includes unlocking your bootloader (which deletes all your data on your phone!!!) and installing magisk. If you don't know much about that process, you better read some basic tutorials first
Click to expand...
Click to collapse
Cool thanks man! Just another quick question - what are we losing by rooting (warranty aside)? OTA updates maybe; what else?
shahriyarali said:
Cool thanks man! Just another quick question - what are we losing by rooting (warranty aside)? OTA updates maybe; what else?
Click to expand...
Click to collapse
Definitely widevine L1 status. That will prevent netflix and other streaming services, that rely on that drm-thing, won't stream in more than 480p. Besides that, I don't remeber anything else...
AAh oh yes, and there will be this strange warning screen each time you boot your phone, which you can't get rid off.
the_brad said:
Holy sh*t, that really works! I've been searching for a solution to that for such a looong time...
Btw, I took the "APTX for Android Ore & Pie"-Module and added your props to the system.prop inside of that module and then I added an empty dummy of RazerAuraBluetoothRes.apk into the (has to be created) folder /vendor/overlay/ inside of the module's /system folder. That way it is systemless and therefore doesn't make any problems regarding AVB, safetynet and whatnotelse
Click to expand...
Click to collapse
So @the_brad, just to put this all together since I'm currently having issues getting this working.
1. Install arter kernel & Magisk
2. Remove /vendor/overlay/RazerAuraBluetoothRes.apk
3. Download and extract "APTX for Android Ore & Pie"
4. Add the quoted props to system.prop from the extracted module.
5. Create a dummy "RazerAuraBluetoothRes.apk" within a newly created folder of the extracted module at "/system/vendor/overlay/"
6. Recompress/package the module back into a zip for install.
7. Install module and reboot.
Did I miss anything?
unstoppablekhaos said:
So @the_brad, just to put this all together since I'm currently having issues getting this working.
1. Install arter kernel & Magisk
2. Remove /vendor/overlay/RazerAuraBluetoothRes.apk
3. Download and extract "APTX for Android Ore & Pie"
4. Add the quoted props to system.prop from the extracted module.
5. Create a dummy "RazerAuraBluetoothRes.apk" within a newly created folder of the extracted module at "/system/vendor/overlay/"
6. Recompress/package the module back into a zip for install.
7. Install module and reboot.
Did I miss anything?
Click to expand...
Click to collapse
Much easier:
1. Install arter kernel & Magisk
2. Remove /vendor/overlay/RazerAuraBluetoothRes.apk
3. Download and extract install "APTX for Android Ore & Pie"
3.1 reboot
4. Add the quoted props to system.prop from inside the installed the extracted module.
5. Create a dummy "RazerAuraBluetoothRes.apk" within a newly created folder inside the installed of the extracted module at "/system/vendor/overlay/"
6. Recompress/package the module back into a zip for install.
7. Install module and reboot.
the_brad said:
Definitely widevine L1 status. That will prevent netflix and other streaming services, that rely on that drm-thing, won't stream in more than 480p. Besides that, I don't remeber anything else...
AAh oh yes, and there will be this strange warning screen each time you boot your phone, which you can't get rid off.
Click to expand...
Click to collapse
I haven't heard of losing widevine. I mean I think of you root systemless you prevent it.
Okazar said:
I haven't heard of losing widevine. I mean I think of you root systemless you prevent it.
Click to expand...
Click to collapse
No, it's definitely gone. You keep L3, but that's not very usefull for anyhing.
I think, it is that way on all android phones as nobody has developed a hack to preserve these keys before bootloader unlock.
So I have a pair of Sennheiser PXC 550s, they have AptX, and I'm honestly not sure how I enable AptX. Followed the instructions since I already had the stock rom w/ kernel and Magisk installed. I can't change any of the Bluetooth options in the Developers options either.
Edit: So I kinda forgot I had to connect to my headphones first, but when I change the codec to AptX in Developer options it reverts back to SBC.
Craftingmod said:
1. Install arter kernel & Magisk
2. Remove /vendor/overlay/RazerAuraBluetoothRes.apk using your favorite explorer - This overlay disables APTX
3. Open /vendor/build.prop using your favorite explorer and search "persist.vendor.bt.a2dp_offload_cap=sbc" and delete line.
After that, add quote to bottom line. and Save.
4. Install "APTX for Android Ore & Pie" from magisk manager (slide left to right -> Downloads -> Search -> Install) and reboot
5. PROFIT :fingers-crossed:
This also enables APTX-TWS (Qualcomm TWS Plus) but I didn't test it because I have no device.
Click to expand...
Click to collapse
Nice work.
Wow I wish this thread received some more attention.
There are so many threads on this problem with other phones, but I couldn't find a workable solution until this.
I was able to follow your guide and get APTX working.
My sound quality does seem better, but it could be placebo, haha.
Either way, finally seeing APTX as the in-use codec is good enough for me.
Thank you!
rogeriskira said:
Thank you so much OP and The Brad. Your method and Brad's systemless is the best combo. In android 9 we don't have AAC, anyway to add those libraries as well?
Click to expand...
Click to collapse
Aac? I connected the shan ling m0 player, the phone shows aac HD audio, but there is a delay of 0.5s. . Very bad.
Hi All,
I installed this from Magisk and removed the stock APK but I could not find the line in build.prop to remove.
In saying this I have a very nice pair of Sennheiser Bluetooth headphones and I can see the HD codec now in Bluetooth but TBH I don't hear any difference?
I have noticed I no longer get a tiny "crackle" every so often while listening to music so I *guess* its working?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}