Database Users

[GUIDE][KNOX-SAFE] How to Root/Mod Australian Telstra 4.4.2 * G900IDVU1ANE1 ONLY!! *

HOW TO ROOT AND MOD YOUR AUSTRALIAN TELSTRA G900I
WITHOUT TRIPPING KNOX
Firmware 4.4.2 G900IDVU1ANE1 ONLY !!
WANAM XPOSED THEMES CAN BE FOUND IN THIS POST
{
"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"
}
Hi fellow Australian Telstra S5 users.
About a week ago I finally got my hands on my Galaxy S5 G900I model.
This has been my 5th Samsung device (GT-I9000, GT-I9100, GT-I9305T, GT-P5100, and SM-G900I), and the first I've encountered the deadly KNOX security.
This is a small guide on how to install SuperSU, Busybox, Xposed Framework, and Wanam Xposed without tripping your KNOX counter.
STARTING OFF
WARNING: MAKE SURE THAT THE KERNEL VERSION AND BUILD NUMBER MATCH YOUR PHONE.
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE, DO THIS AT YOUR OWN RISK !!
First of all, download the G900IDVU1ANE1_Mods-djb77 file attached to this post, this contains all the files and resources you need.
The original files can be found in the G900IDVU1ANE1_Original zip file.
This Mods zip file contains the following:
ROOTING TOOLS: Towelroot - SuperSU - Busybox (Stericson)
APPS: AdAway - Phone INFO - Titanium Backup - Total Commander
XPOSED APPS: Xposed Installer - Wanam Xposed - XSecureStorage
OTHER FILES: Modded others.xml - Original Samsung Bootanimation - Wanam Xposed Presert
The modded others.xml file is the same as the original others.xml except for the following changes:
- Show proper SMS / MMS timestamp (when the item was sent, not recieved)
- Disable the Software Update Menu
- Enable Call Button in Contact List
PREPARING FOR ROOT
- Go to Settings -> General -> About Device -> Software Updates, uncheck Auto-update and Wi-Fi only.
- Go to Settings -> General -> Security, check Unknown Sources, and uncheck Verify apps.
- Go to Settings -> General -> Security -> Security Policy Updates, disable Automatic Updates.
- Copy downloaded files to your SD Card.
INSTALLING ROOT / BUSYBOX
- Install Towelroot and launch. Press the "Make it Ra1n" button and wait, the app will prompt you when its finished.
- Install SuperSU and launch. Install SU Binary via Nomral option, and don't disable KNOX.
- Restart Phone.
- Install Busybox and launch. Wait for Small Install to finish loading, then press the Install button. Restart Phone.
RESTORE SAMSUNG BOOTANIMATION (Optional)
This removes the Telstra branded bootaniatmion / shutdown with the stock Samsung bootanimation / shutdown
- Install Total Commander
- Launch Total Commander and delete the following files
/system/media/bootsamsung.qmg
/system/media/video/shutdown/shutdown.qmg
/system/media/audio/ui/PowerOn.ogg
- Copy the files from the Bootanimation folder over to these locations, with chmod 644 on the new files.
FIX MICROSD CARD WRITE PERMISSIONS (Optional)
- Install Total Commander (if you haven't already)
- Launch Total Commander and delete the following file
/system/etc/permissions/platform.xml
- Copy the files from the MicroSD folder over to that location, with chmod 644 on the new file.
ADD EXTRA CSC FEATURES (Optional)
- Install Total Commander (if you haven't already)
- Launch Total Commander and delete the following file
/system/csc/others.xml
- Copy the files from the CSC folder over to that location, with chmod 644 on the new file.
INSTALL XPOSED FRAMEWORK / WANAM XPOSED (Optional)
- Go to Settings -> Applications -> Application manager, uninstall any updates for S Health and HealthService.
- Install Xposed framework + apps, but don't open them just yet.
- Launch Xposed Framework installer with all modules ticked. Restart Phone.
- Copy Standard Settings.wx to .WanamXposed folder.
- Launch Wanam Xposed and load the Standard Settings. Restart Phone.
Hope this little guide helps some of you out
Enjoy your modded G900I with genuine KNOX

and for OS above NE1, refer here:
http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044

Just a shame we can't use Mobile ODIN, otherwise I'd look at deodexing the ROM and doing some further modifications.
I hear that it trips KNOX, and if that's the case I'm staying well clear of it.

djb77 said:
Just a shame we can't use Mobile ODIN, otherwise I'd look at deodexing the ROM and doing some further modifications.
I hear that it trips KNOX, and if that's the case I'm staying well clear of it.
Click to expand...
Click to collapse
Mobile ODIN (Pro version) does not trip knox only the simple version does

wajiman said:
Mobile ODIN (Pro version) does not trip knox only the simple version does
Click to expand...
Click to collapse
So you've tried it and can confirm it's all good? Sorry to be extra-cautious lol

This is what scares me, that bottom warning... Did you get the same warning screen?
I'm using the Pro version too...

djb77 said:
This is what scares me, that bottom warning... Did you get the same warning screen?
I'm using the Pro version too...
Click to expand...
Click to collapse
yes i did, but it does not trip knox, and you can also flash zip files through mobile odin (OTA/Update option) but it requires some additional things for the zip to work perfectly. @_alexndr know about it, i flashed his rom that way.
but in my thread, i havent mentioned anything about Mobile Odin, only PC Odin

wajiman said:
yes i did, but it does not trip knox, and you can also flash zip files through mobile odin (OTA/Update option) but it requires some additional things for the zip to work perfectly. @_alexndr know about it, i flashed his rom that way.
but in my thread, i havent mentioned anything about Mobile Odin, only PC Odin
Click to expand...
Click to collapse
What additional things are you talking about? Is it something in the updater-script, does the zip need to be signed?
I just made a deodexed version of this ROM with ArchiKitchen so I'm keen to flash the deodexed system files and framework.

djb77 said:
What additional things are you talking about? Is it something in the updater-script, does the zip need to be signed?
I just made a deodexed version of this ROM with ArchiKitchen so I'm keen to flash the deodexed system files and framework.
Click to expand...
Click to collapse
i have no idea, this is what he told me when i asked him:
_alexndr said:
Yes, you can. Most of CWM flashable zip files should work. Unfortunatelly, some devs in their zip files do not care about compatibility with MOP and use mount points specific for CWM/TWRP. Here is an example of not working zip using Mobile Odin Pro (reported in my thread @ Polish forum):
[THEME] All Backs Black S5 ••●The Blackness Realm●••
Above zip file can't be succesfully flashed using MOP because it contains /sdcard mount point for internal emulated SD card (in updater-script AND in sh scripts). Unfortunatelly - such mount point does not exists in case of MOP... If the dev/themer would change the point on the other (/sdcard -> /data/media/0) then such zip file will be compatible with all custom recoveries AND with Mobile Odin Pro
BTW
Note that if you flash using MOP zip file containing custom recovery or custom kernel - then your KNOX will be tripped !!!
Click to expand...
Click to collapse

OK that seems pretty straight forward to understand. Make sure the partition mounts are compatible with Mobile ODIN Pro (which my updater-scripts usually are) and don't flash kernel, recovery, or modem. Too easy

THEMES FOR WANAM XPOSED
To install these themes, extract the zip file and copy the .wx file to your .WanamXposed folder on your Internal SD Card.
This is what the standard quicksettings screen and device settings screen look like:
The first thing that is changed in all the themes is that terrible blue colour that is used for the backgrounds, as shown below.
Please note that not all apps are supported by this function, however it does work on a few (even 3rd party market apps)
BLACK AND BLUE
BLACK AND GREEN
​

Guide updated to v2, to include a fix for the MicroSD Card. I noticed the issue when trying to use Titanium Backup

[GUIDE][XT1254]Getting Xposed Working

Guide: Getting Xposed Running​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!
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!!!

[Guide] [ROOT Required] Installing Viper4Android on Lollipop

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!!!

[Tutorial] permanent fix for notifications issue

Hi guys.
First of all, all credits go to @ZeroPDA. The processo is from him. Im just making this tut for everyone to see.
Requirements - root
1-download root explorer and terminal emulator
2-download universal init.d
3-go in the universal init.d APP and turn it on.
4- go in root explorer, go to etc/init.d and create a filé named deviceidle. Note that you have to give all permissionários to etc folder and init.d folder in order to be allowed to creat the file.
5-open the file that you just created, deviceidle, with a text editor, and write the line "dumpsys deviceidle disable". Save. Nós erase everything else from the folder init.d.
VERY IMPORTANT - BEFORE THE BELOW 6 STEP, GO TO SETTINGS, ADMIN PERMISSIONS, AUTO INICIALIZE APPS AT BOOT, AMD GIVE PERMISSION TO UNISERSAL iNIT.D
6-reboot your phone.
7-please allow some seconds when it boots, to see the message that universal init.d has been granted with supersu permissionários. This may take 30 seconds after boot.
8-when you see the message, go in terminal emulator and type "su"
9-type "dumpsys deviceidle enabled". If it returns 0 your good to go. If it returns 1 you've done something wrong.
Gonna include a video recorded imeadiatly after boot
New video with steps
https://youtu.be/-FJ6YsVJgxM

Did not work, getting 1 and I redid and followed every step.

Thank you for recognizing my efforts. I decided to make it even more clearer with reference to the apps
Requirements - root
Download root explorer and Terminal Emulator for Android
Download Universal Init.d
Go in the Universal init.d app and turn it on.
Go in root explorer, go to /etc/init.d and create a file named deviceidle with permissions rw- --- --- (Only Owner can Read and Write).
Open the file that you just created, deviceidle, with a text editor, and write the line dumpsys deviceidle disable. Save. You can delete everything else from the folder /etc/init.d Just leave one file deviceidle there (You can also leave 99SuperSUDaemon if it is present)
Reboot your phone.
Please allow some seconds when it boots, to see the message that Universal init.d has been granted with supersu permissions. This may take 30 seconds after boot.
After seeing the message, go to the terminal emulator and type "su"
Type "dumpsys deviceidle enabled". If it returns 0 your good to go. If it returns 1 you've done something wrong.

New vídeo with the steps
https://youtu.be/-FJ6YsVJgxM

I did these exact steps, does still not work..

MFRCNS said:
I did these exact steps, does still not work..
Click to expand...
Click to collapse
do it again. sometimes you have to check the permissions again. at first, with me, i had to check them twice. also, put all permissions in the file created. when yoiu reboot, please allow a few seconds till the message "universal init.d has been granted su privileges"

I writed a new step. its very importan and might be the reason some people arent being sucessfull with this.
before you reboot the phone, GO TO SETTINGS, ADMIN PERMISSIONS, AUTO INICIALIZE APPS AT BOOT, AnD GIVE PERMISSION TO UNISERSAL iNIT.D

For some reason this method does not work for me
I donwload and install everything, but when i try to go through the steps this is what happens:
I open universal init.d and nothing happens , no way to turn it on!
Then, in Root Browser i have no init.d folder inside etc and if i try to create it, the browser gets stuck and no folder is created!!! Please Help

maurosch said:
For some reason this method does not work for me
if i try to create it, the browser gets stuck and no folder is created!!! Please Help
Click to expand...
Click to collapse
Probably either you are not rooted or not given root permissions.

ZeroPDA said:
Probably either you are not rooted or not given root permissions.
Click to expand...
Click to collapse
thank you for your reply. I am rooted and permissions for the etc folder are 777 all clicked!!!i want to do this cause i really miss notifications!!!! at first they work, but after a while i have to reboot the phone to start getting them again!!!

What kind of notification doesn't work? GMail, WhatsApp, Viber? All of them?
Sent from my HUAWEI M2-A01L using Tapatalk

maurosch said:
thank you for your reply. I am rooted and permissions for the etc folder are 777 all clicked!!!i want to do this cause i really miss notifications!!!! at first they work, but after a while i have to reboot the phone to start getting them again!!!
Click to expand...
Click to collapse
give permissions to etc folder and also to init.d folder. when you create the deviceidle file, before you write anything, save the file without nothing and give also full permissions to that file

nosidefcp said:
give permissions to etc folder and also to init.d folder. when you create the deviceidle file, before you write anything, save the file without nothing and give also full permissions to that file
Click to expand...
Click to collapse
i have been usinf this method for awhile, and has worked perfectly.
but since i am on a different firmware now, i had to redo it, and yes it still works...
BUT, only for some time and then it reverts back. (so when checking in Terminal it reads 0, and stays like that for an hour or two, and then automatically turns to 1)
Sent from my HUAWEI NXT-AL10 using XDA Labs

I tried it the first time did not work. Then I opened the Universal Init app and it showed ON and below were the scripts, so I went to SuperSu app to make sure Init app gained permissions, and that was the problem it didn't work in the beginning because did not gain Root. So, went back to the Init app and click the TEST button at the bottom, and there appeared the SuperSu window asking for Root permissions, so, granted permissions, rebooted the phone and opened terminal to make sure it worked this time. SUCCESS, it showed 0 this time. I don't know if it changes back to 1 like someone mentioned above, but I'll check and come back here. Good luck

maurosch said:
thank you for your reply. I am rooted and permissions for the etc folder are 777 all clicked!!!i want to do this cause i really miss notifications!!!! at first they work, but after a while i have to reboot the phone to start getting them again!!!
Click to expand...
Click to collapse
Freeze phone manager. I'm not sure how people are reporting success with this when doze is a feature for all Marshmallow devices and none have this issue. I have no doubt that the problem is with phone manager and I'm sure if we were able to decompile the file properly there would already be a solution.

On B321 after selecting keep wifi on during sleep and keep mobile data on during sleep I have zero notification issues. I don't even have to move any apps to system/app anymore.

The problem is that there is no B321 for L29 officially. Any try to flash B321 to L29 is connected with risk to brick the phone. And there is no reliable guidance how to return back to B180 from B321 if someone doesn't like it.

ajsmsg78 said:
On B321 after selecting keep wifi on during sleep and keep mobile data on during sleep I have zero notification issues. I don't even have to move any apps to system/app anymore.
Click to expand...
Click to collapse
I couldnt find "keep mobile data on during sleep" option. Where is it?

hi my friend
testing this tip
for lock app after sleep facebook line email etc. show noti. but drain batt'
unlock after sleep not show noti. but save batt.
making by wipe down lock frist wipe down unlock second make in recent app
looking at image
{
"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"
}

b180 fixed the gmail notification issue for me, it is already stated in the official change log that it fixes gmail notification.
That's maybe why the report for b180 drains more battery, doze is half disabled on b180 but so far the notification is working like it should.

Collective Dolby Atmos® Nougat Port Thread [Unity][Deprecated]

{
"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"
}
This is the Dolby Atmos ported from BQ Aquaris X5 and Lenovo K6 stock Nougat ROMs. Like with @guitardedhero's ZTE Axon 7 Dolby Atmos Oreo port, it requires the stock audioserver from the roms. This greatly limits it's compatibility and likely won't work on devices/roms with a lot of audio customization. However it should work on most
Huge thanks to @ahrion who taught me everything I know about app porting
These installers utilize my Unity installer that will install the mod to magisk or system depending on the device setup and will prepare it for any root solution (for anything other than magisk, supersu, and phh superuser, you will need init.d support)
Troubleshooting:
Audio Mod Troubleshooting Guide
Installation/Upgrade:
Flash the zip and your done! If your flashing a newer version of this mod, the installer will detect the old one and perform an upgrade
Uninstallation:
Just flash the zip again and it'll detect the current install and uninstall it. Pretty easy huh?
Magisk Version Compatibility:
v15.3 - v18.1
DOWNLOAD
Credits of Originality:
- Dolby
- BQ
- Lenovo
XDA:DevDB Information
Collective Dolby Atmos® Nougat Port Thread [Unity], App for the Android General
Contributors
Zackptg5
Version Information
Status: Stable
Current Stable Version: v1.8
Stable Release Date: 2019-01-16
Created 2019-01-24
Last Updated 2020-01-01

Great work , the new UI is awesome , and the dynamic mode is a very good addition to the old modes
Thanks ?
Sent from my X5 Plus using XDA Labs

:highfive:

Sorry but not work on my Redmi 4x RR 5.8.5 7.1OS. FC.

repey6 said:
Sorry but not work on my Redmi 4x RR 5.8.5 7.1OS. FC.
Click to expand...
Click to collapse
Can you go over the troubleshooting section of the op?

Zackptg5 said:
Can you go over the troubleshooting section of the op?
Click to expand...
Click to collapse
Sorry.Not other mod . Clear installation. Log maybe later. And can't unistall it.

@Zackptg5, flashed this Dolby-BQ-X5-v1.0.zip in twrp_3.0.2-1_sm-a310 (Samsung exynos SM-A310F) on clean stock nougat 7.0, no boot even when restoring original audioserver. Only exit is restoring system. Recovery.log and system space screenshot attached.

mohand06 said:
@Zackptg5, flashed this Dolby-BQ-X5-v1.0.zip in twrp_3.0.2-1_sm-a310 (Samsung exynos SM-A310F) on clean stock nougat 7.0, no boot even when restoring original audioserver. Only exit is restoring system. Recovery.log and system space screenshot attached.
Click to expand...
Click to collapse
The recovery log outlines the problem: you have no space left in your system partition. The tricky thing with audioserver is that it requires proper permissions and chcon set or you won't be able to boot. When you flash this mod again to uninstall it, it restores stock audioserver and sets those permissions but since the install itself never finished, there's no telling what would happen. I recommend switching to magisk as it stores all of its mods on your /data partition which would avoid this problem

Zackptg5 said:
The recovery log outlines the problem: you have no space left in your system partition. The tricky thing with audioserver is that it requires proper permissions and chcon set or you won't be able to boot. When you flash this mod again to uninstall it, it restores stock audioserver and sets those permissions but since the install itself never finished, there's no telling what would happen. I recommend switching to magisk as it stores all of its mods on your /data partition which would avoid this problem
Click to expand...
Click to collapse
The attached screenshot of system partition shows that there's 206.08Mb space available. Restored audioserver with 0755 permissions. Thus the issue is elsewhere. Fyi, I used to flash each of gh's Dolby Atmos™ for Oreo test builds and I always manage to get out of the no boot issue by the audio server restoring trick.
As for using magisk, which I tried and have sometimes the issue of no apps in drawer though modules present in magisk, I still feel more comfortable with supersu. Thanks for your reply.

mohand06 said:
The attached screenshot of system partition shows that there's 206.08Mb space available. Restored audioserver with 0755 permissions. Thus the issue is elsewhere. Fyi, I used to flash each of gh's Dolby Atmos™ for Oreo test builds and I always manage to get out of the no boot issue by the audio server restoring trick.
As for using magisk, which I tried and have sometimes the issue of no apps in drawer though modules present in magisk, I still feel more comfortable with supersu. Thanks for your reply.
Click to expand...
Click to collapse
That's not enough. You need to do this:
Code:
chown 0:2000 /system/bin/audioserver
chmod 0755 /system/bin/audioserver
chcon u:object_r:audioserver_exec:s0 /system/bin/audioserver
The no space error actually referred to the /system/vendor folder so I'm not sure how you're partition layout is. The only time modules won't show up in magisk is when there's a bad post-fs-data script that errors out and/or takes too long to finish. Magisk is easier because you can just delete the module folder and be done with it

Perfectly work with redmi note 4(mido) on official miui beta rom with magisk..The Ui is fantastic...but i wonder what demo actually do..i just see the slideshow but none of any sound.. @[email protected] ..nah but i dont care much about it as long the mod work . 1 more things is when i install it alongside with ainur sauron...the dolby atmos will crash.... But without ainur it works like charm.

Zackptg5 said:
That's not enough. You need to do this:
Code:
chown 0:2000 /system/bin/audioserver
chmod 0755 /system/bin/audioserver
chcon u:object_r:audioserver_exec:s0 /system/bin/audioserver
The no space error actually referred to the /system/vendor folder so I'm not sure how you're partition layout is. The only time modules won't show up in magisk is when there's a bad post-fs-data script that errors out and/or takes too long to finish. Magisk is easier because you can just delete the module folder and be done with it
Click to expand...
Click to collapse
OK that's fine, I understand that I can't install the new dolby on my system by flashing the zip in recovery as I don't intend to switch to magisk for now.
I used to manually install v4a, what about manually installing dolby? Would you direct me what to install and where. I know for the permissions. Thanks

Nightdemon1999 said:
Perfectly work with redmi note 4(mido) on official miui beta rom with magisk..The Ui is fantastic...but i wonder what demo actually do..i just see the slideshow but none of any sound.. @[email protected] ..nah but i dont care much about it as long the mod work . 1 more things is when i install it alongside with ainur sauron...the dolby atmos will crash.... But without ainur it works like charm.
Click to expand...
Click to collapse
Sound doesn't work? Works for me. In order to use multiple audio mods like sauron and dolby together with magisk, you need to flash audio modification library (it's also on magisk repo)
mohand06 said:
OK that's fine, I understand that I can't install the new dolby on my system by flashing the zip in recovery as I don't intend to switch to magisk for now.
I used to manually install v4a, what about manually installing dolby? Would you direct me what to install and where. I know for the permissions. Thanks
Click to expand...
Click to collapse
If you unzip the installer, all of the files are in the path they would be normally installed into (system folder) so just copy that layout. Although unless you cleared up some space, it won't work. In which case if you do clear some space, you're better off just flashing the zip. It also installed boot scripts and addon.d script which are generated by the installer depending on your device setup so an alternative to the scripts would be setting selinux to permissive

Zackptg5 said:
Sound doesn't work? Works for me. In order to use multiple audio mods like sauron and dolby together with magisk, you need to flash audio modification library (it's also on magisk repo)
Click to expand...
Click to collapse
Okay after im tried again it did not work..after first reboot..but after second time reboot both ainur and dolby working ..tq for u help :good:

Help, please! My phone samsung J710FN can't boot stuck at samsung logo after install via Magisk.

Tung Lam said:
Help, please! My phone samsung J710FN can't boot stuck at samsung logo after install via Magisk.
Click to expand...
Click to collapse
Are you on stock samsung? Not surprised this doesn't work. Audioserver keeps crashing due to it not containing some stuff needed for some other libraries present on your device. There's not much I can do about it so it's just not compatible with your device unfortunately. You can flash the zip again and it'll uninstall it

Zackptg5 said:
Are you on stock samsung? Not surprised this doesn't work. Audioserver keeps crashing due to it not containing some stuff needed for some other libraries present on your device. There's not much I can do about it so it's just not compatible with your device unfortunately. You can flash the zip again and it'll uninstall it
Click to expand...
Click to collapse
I'm on a custom touchwiz ROM.

Hello,Zackptg5
Is there a solution for this sound module to work on my Nexus 7 2012 aosp rom 7.1.2
The installation runs without worries but I have got force close by opening the application Dolby Atmos...
Thanks for help...

laugeek57 said:
Hello,Zackptg5
Is there a solution for this sound module to work on my Nexus 7 2012 aosp rom 7.1.2
The installation runs without worries but I have got force close by opening the application Dolby Atmos...
Thanks for help...
Click to expand...
Click to collapse
Can you run through the troubleshooting guide and see if any of the listed solutions solves it? Try setting selinux to permissive too

Zackptg5 said:
Can you run through the troubleshooting guide and see if any of the listed solutions solves it? Try setting selinux to permissive too
Click to expand...
Click to collapse
Selinux to permissive again force close any solutution ?