Database Users

Viper4Android S-ON/OFF Workaround

I have successfully created my own bypass to get viper4android to work. Always create a full backup before attempting =)
1. Download viper4android APK
2. Download Root Explorer from the playstore
3. Install Both Apps
4. Launch Root Explorer
5. In root explorer go to /system/lib/soundfx and copy the folder to /data/ (make a soundfx folder)
6. Also copy /system/etc/audio_effects.conf to the /data/soundfx/ folder
7. Using root explorers menu you can create a shortcut (symbolic link) make a shortcut of the /data/soundfx/ folder and a shortcut of the /data/soundfx/audio_effects.conf
8. Boot into TWRP
9.Mount the system partition
10. Rename /system/lib/soundfx to /system/lib/soundfx2
11. Copy soundfx shortcut create earlier to /system/lib/ it will look like a "file" to TWRP
12.Rename the /system/etc/audio_effects.conf to /system/etc/audio_effects.conf1
13. Copy the audio_effects shortcut into /system/etc/ (be sure its name matches the old exactly)
15. Reboot
16. Launch Viper and install driver
I haven't dealt with LPA yet (hasn't had an issue) nor have I done any other modifications at this time which are avail on the viper4android thread.
I was just thinking about symbolic links to get around this S-OFF/ON issue and it appears they work and technically as a workaround we could symbolically link everything in system to another location and access it all. This could easily be put into ROM builds now at least as well!
Build.Prop may be useful to move out via sym link as well

It's not a matter of being s-on or s-off.. It's a matter of having write protection removed then you can do all of that. S-off just allows you to flash any partition on the device.. (radio, hboot etc..) plus you can flash any ruu you want as long as you change to supercid
There is a kernel module in dev and it's working great on my device.

On M7 it seems to me that the S-OFF also disables write protection system on stock rom
Envoyé de mon HTC Butterfly s en utilisant Tapatalk

migascalp said:
On M7 it seems to me that the S-OFF also disables write protection system on stock rom
Envoyé de mon HTC Butterfly s en utilisant Tapatalk
Click to expand...
Click to collapse
But you don't need s-off to disable write protection. You just need a kernel with it disabled or the kernel module which flair posted in the development section. I'm using it and am able to write to the system fine and I'm s-on. The title of the thread should be something like "with write protection on" not s-on.

I just wanted to clarify that with S-OFF this module is useless

migascalp said:
I just wanted to clarify that with S-OFF this module is useless
Click to expand...
Click to collapse
You don't need to clarify that to me. I'm very well aware of that. My point was that for this topic you don't need s-off for this to work.. You just need write protection off. Whether that be with with s-off or with a module.. This working is not dependant on s-off.. It's dependant on write protection being off. That is my point.
Sent from my HTC One using Tapatalk

For anyone who wants the stock kernel with write protection off just use this JMZM8 Kernel and then just install busybox like regular and boom Viper4Android, literally made my M8 sound so much better (not that it wasn't already awesome)

worked with htc 816 running indian stock, which still has no s-off at the moment,
had to go to twrp recovery terminal command, to make the symbolic links or move directories....
viper4android made a lot of difference in this particular model.
the next thing would be to make viper4a a system app, since it tended to close and thus lower the volume, usually after some time.

helloicanseeu said:
worked with htc 816 running indian stock, which still has no s-off at the moment,
had to go to twrp recovery terminal command, to make the symbolic links or move directories....
viper4android made a lot of difference in this particular model.
the next thing would be to make viper4a a system app, since it tended to close and thus lower the volume, usually after some time.
Click to expand...
Click to collapse
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off

One-M8-Master said:
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
Click to expand...
Click to collapse
will try to make it work .... meanwhile from what i gathered in a htc 816 facebook group, most indian pple buying this particular model seems to have no clue about making the most out of its audio properties ... the 816's true selling points were its larger 5.5 " size, great audio output, and relatively low cost compared with other htc flagship models.

One-M8-Master said:
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
Click to expand...
Click to collapse
done ... went to twrp recovery,
moved "com.vipercn.viper4android_v2-1.apk" from ""/data/app" to "/system/priv-app"
moved "com.vipercn.viper4anddroid_v2-1/libV4AJniUtils.so" from to "/data/app-lib" to "/system/lib/"
should be working fine, havent extensively tested it out yet though,
reported as a system app, and viper driver is running.

I Can't Get data/soundfx Shortcut to Transfer to /System/lib
In the opening instructions, #11 says that we have to transfer the data/soundfx shortcut to /system/lib. Everytime I try it with TWRP it just says failed. If I try it with root browser,
it will say successful until the phone is rebooted. Any help would be appreciated. I am a newbie to these things.

BaltColts said:
In the opening instructions, #11 says that we have to transfer the data/soundfx shortcut to /system/lib. Everytime I try it with TWRP it just says failed. If I try it with root browser,
it will say successful until the phone is rebooted. Any help would be appreciated. I am a newbie to these things.
Click to expand...
Click to collapse
u need to install twrp recovery for htc 816.
get it from "TeamWin Projects" website.
after successfully installing twrp, boot into recovery mode, use twrp to move data/soundfx shortcut to /system/lib, etc...
hope u get to install viperfx successfully and make full blast of the great audio output of this big value music machine, makes a near perfect combo with my music angel cube speakers(as far as mine human ears tell me), anyone using this combo too?
later htc models based on mediatek chipsets seem to have horrible audio outputs ... maybe even iphone 6 and samsung note4 cant beat htc 816 where mp3 output is concerned
background: htc 816 doesnt has s-off, so its always s-on, which means if u try to write to the "/system" folder, the phone will trigger a reboot immediately, to prevent any modifications to the folder. root browser will not be able to write to /system folder, even if the phone has root access, due to this s-on protection. The only way to edit /system folder is to boot to twrp (in recovery mode).

blewis540 said:
I have successfully created my own bypass to get viper4android to work. Always create a full backup before attempting =)
1. Download viper4android APK
2. Download Root Explorer from the playstore
3. Install Both Apps
4. Launch Root Explorer
5. In root explorer go to /system/lib/soundfx and copy the folder to /data/ (make a soundfx folder)
6. Also copy /system/etc/audio_effects.conf to the /data/soundfx/ folder
7. Using root explorers menu you can create a shortcut (symbolic link) make a shortcut of the /data/soundfx/ folder and a shortcut of the /data/soundfx/audio_effects.conf
8. Boot into TWRP
9.Mount the system partition
10. Rename /system/lib/soundfx to /system/lib/soundfx2
11. Copy soundfx shortcut create earlier to /system/lib/ it will look like a "file" to TWRP
12.Rename the /system/etc/audio_effects.conf to /system/etc/audio_effects.conf1
13. Copy the audio_effects shortcut into /system/etc/ (be sure its name matches the old exactly)
15. Reboot
16. Launch Viper and install driver
I haven't dealt with LPA yet (hasn't had an issue) nor have I done any other modifications at this time which are avail on the viper4android thread.
I was just thinking about symbolic links to get around this S-OFF/ON issue and it appears they work and technically as a workaround we could symbolically link everything in system to another location and access it all. This could easily be put into ROM builds now at least as well!
Build.Prop may be useful to move out via sym link as well
Click to expand...
Click to collapse
Will this method work without busybox?
There is a very specific reason why I'd not like to use busybox, so this may end up being a very good solution for me.

fade2black101 said:
Will this method work without busybox?
There is a very specific reason why I'd not like to use busybox, so this may end up being a very good solution for me.
Click to expand...
Click to collapse
What's wrong with busybox? its a hidden process only used when an app like V4A calls for it, other then that it has no negative effect. why avoid it?
Besides this thread is disinfo, all this is not required to get V4A working, Go to this thread Here and follow instructions.

hi,
I have completed those steps, but the viper4android keeps asking me to install the driver.
I have tried also the steps from helloicanseeu. But still, not working.
please help me, because installing viper4android is never been this hard on my previous device. thank you.

i got stuck after flashing viper . stuck on htc logo then reboots back to recovery..

oulixeus said:
hi,
I have completed those steps, but the viper4android keeps asking me to install the driver.
I have tried also the steps from helloicanseeu. But still, not working.
please help me, because installing viper4android is never been this hard on my previous device. thank you.
Click to expand...
Click to collapse
Which phone u using? What stock rom? I was using stock indian on htc816.
---------- Post added at 09:12 PM ---------- Previous post was at 09:03 PM ----------
XskipperX said:
i got stuck after flashing viper . stuck on htc logo then reboots back to recovery..
Click to expand...
Click to collapse
U followed the steps by blewis?

Why it is so complicated..???.if s-on, unlock bootloader and flash a custom kernel (elementalx). In install options just choose to set SElinux permissive. Then, install driver for Viper and reboot. That is it. If s-off, start with kernel installation...
People are talking about that s-off gives full access to system partition - true but not correct. Unlocked bootloader gives write access to system folder, while s-off in addition allows to change partitions, bootloader, etc.
Sent from my HTC One M8 using XDA Free mobile app

uvt_novice said:
Why it is so complicated..???.if s-on, unlock bootloader and flash a custom kernel (elementalx). In install options just choose to set SElinux permissive. Then, install driver for Viper and reboot. That is it. If s-off, start with kernel installation...
People are talking about that s-off gives full access to system partition - true but not correct. Unlocked bootloader gives write access to system folder, while s-off in addition allows to change partitions, bootloader, etc.
Sent from my HTC One M8 using XDA Free mobile app
Click to expand...
Click to collapse
Welp, it's so complicated because NONE of the instructions seem to work for a huge number of us. I've tried like 5 "failsafe" methods but they just fail and fail.
ONE time I had it working and was all psyched, and then I restarted the phone at some point and that was the end of that. Never worked since.

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

AdAway on stock nougat- copying of host file failed

hello im getting the following message everytime i try and download the lists "copying of host file failed! please read help for more information"
ive just updated to the android 7.0 through the developer program, twrp custom recovery installed with root access build number NRD90M
just wondering what could be causing this and if i can do anything to try and fix it thanks

Is your /system set to read only, or read/write? If read only, adaway will not be able to update /system/etc/hosts

dratsablive said:
Is your /system set to read only, or read/write? If read only, adaway will not be able to update /system/etc/hosts
Click to expand...
Click to collapse
i have it set to read write im gonna try to flash the systemless hosts right now ill update how it goes

flashing the AdAway_systemless_hosts_v2.zip in the recovery, then unistalling and reinstalling the app seems to have worked

you can also use Magisk now to enable complete systemless root and then the hosts file /system/etc will be forwarded to the systemless version

I didn't even install Adaway, I just downloaded a host file and replaced it in /etc/
Works good enough for me and one less app running...

kennehh said:
hello im getting the following message everytime i try and download the lists "copying of host file failed! please read help for more information"
ive just updated to the android 7.0 through the developer program, twrp custom recovery installed with root access build number NRD90M
just wondering what could be causing this and if i can do anything to try and fix it thanks
Click to expand...
Click to collapse
In the exact same boat. Frustrating. Tried Adfree, to no avail. Adaway, to no avail. Tried the adaway bind zip file, making hosts writable, and even System to writable. Nothing.

treoo0_1 said:
In the exact same boat. Frustrating. Tried Adfree, to no avail. Adaway, to no avail. Tried the adaway bind zip file, making hosts writable, and even System to writable. Nothing.
Click to expand...
Click to collapse
i have fixed this by converting adaway from user apps to system apps using Link2SD, reboot and adaway working properly again

Very old thread, but I've had exactly the same problem installing AdAway on the last 3 or 4 phones -- all but one running Nougat 7.0, the other on Oreo 8.1. This was when trying to install AdAway versions 3.1 and 3.3.something.
I finally got it to write hosts file updates using one of the following, not sure which was the key:
-- Installed version 3.2 which had been running problem-free on an old phone for years. The biggest difference is this older phone is running Resurrection Remix 5.8.3 (Nougat 7.1.2).
-- Before trying to update the hosts file on this fresh install, I went straight to AdAway preferences and set "Check for updates daily", "Enable webserver", and "Start webserver on boot". After making those settings I tapped Download Files and Apply Ad Blocking, and it successfully wrote to the hosts file.
Again I don't know which was the fix. It seems weird that version 3.2 would work when a version just before and after it didn't work for me. But of course it is possible that the version is the difference. It seems even more weird that those 3 little preference settings make any difference at all . . . unless it's just the act of writing changes to the AdAway app itself.
Before installing 3.2, using Root Explorer I checked permissions on the working phone and one non-working phone, for the systems and etc folders, and for the hosts file itself. (In all cases AdAway is/was set to use /systems/etc/hosts.) I also checked Android permissions in the Apps list. All permissions were exactly the same on both phones: 0755 for system, 0755 for etc, and 0644 for hosts. No permissions assigned via Android.
Hoping this bump will also get fresh attention from somebody who might know the details of a real answer.

@Moondroid
Why the hell you trying to make some really old ass version of it work instead of installing the newest version? Lol
I've been using 4.2.7 and though its kind of weird on a fresh install I need to update and apply the hosts twice before searching for newer hosts comes back its up to date. But at least it works.

Cam 2

On stock ROM, I can not edit the build prop because it just gives me system can not be mounted errors and on custom ROMs (7.1 because I can't use 8.0 due to WiFi calling and volte not working for me) I am able to edit the build prop just fine but then the camera won't launch. After deleting the line and restarting cameras still don't work. What gives?

you have to restore your build.prop permission to rw-r-r

jackydroid68 said:
you have to restore your build.prop permission to rw-r-r
Click to expand...
Click to collapse
Stock it won't let me do that. I prefer stock so I wish I could remember how I fixed the Mount issue. I believe I've done it before.

Are you stock and rooted... or just "stock" and using TWRP to modify the file? If you are using TWRP to modify the file, you will have to change it's permissions with adb in TWRP after you have mounted system read-write in TWRP, like this:
Code:
adb shell
cd system
chmod 644 build.prop
- Source

acejavelin said:
Are you stock and rooted... or just "stock" and using TWRP to modify the file? If you are using TWRP to modify the file, you will have to change it's permissions with adb in TWRP after you have mounted system read-write in TWRP, like this:
- Source
Click to expand...
Click to collapse
I'm stock rooted. However on stock rom, it won't even let me mount the system in TWRP. I check the box and nothing happens.

carnivalrejectq said:
I'm stock rooted. However on stock rom, it won't even let me mount the system in TWRP. I check the box and nothing happens.
Click to expand...
Click to collapse
Since your not really explaining how you are trying to do it, I am going to assume adb (which is easiest)...
Code:
adb shell
su
mount -o rw,remount -t ext4 /system
chmod 644 /system/build.prop
if the mount command doesn't work, try it like this...
mount -o rw,remount /dev/block/dm-0 /system
Then exit and reboot the phone, should be good after that.
I haven't tried rooting my G5 yet, probably never will, but I do know that many newer phones have special security in place and you cannot remount from adb.
I assume you have tried mounting /system RW in ES File Manager or Solid Explorer?

acejavelin said:
Since your not really explaining how you are trying to do it, I am going to assume adb (which is easiest)...
if the mount command doesn't work, try it like this...
mount -o rw,remount /dev/block/dm-0 /system
Then exit and reboot the phone, should be good after that.
I haven't tried rooting my G5 yet, probably never will, but I do know that many newer phones have special security in place and you cannot remount from adb.
I assume you have tried mounting /system RW in ES File Manager or Solid Explorer?
Click to expand...
Click to collapse
Yeah I haven't even tried it through adb yet because my laptop is slow as molasses but I have tried through TWRP and solid explorer. Everything mounts fine on custom roms, just not stock.

I just went through this a few days ago, I was going bonkers. I managed in the end to mount system in TWRP, but it was like a different set of files... build.prop was there, I pulled it, edited, and pushed it back, but reboot into system had a DIFFERENT build.prop. Made no sense. I rebooted back into TWRP, mounted system again, found the build.prop there had my changes. It was like there were two versions of /system, one that TWRP gave me and one that the system used. It was maddening, to say the least. Somewhere around 2 or 3am, I started getting sloppy trying to get to the bottom of all this, and I accidentally deleted my system partition and soft bricked the phone.
Thankfully I found this thread:
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
These are stock roms that are flashable in TWRP, but modified in that Dm-verity and force encryption have been disabled in the boot images. With this installed, my phone booted properly again and TWRP had no problem accessing the file system... and thankfully this time around, it was the same /system being mounted as the booted phone, everything actually made sense for a change.
I would strongly recommend flashing that modified stock rom and starting over. Camera2 and everything are running properly and I couldn't be happier.

Dishe said:
I just went through this a few days ago, I was going bonkers. I managed in the end to mount system in TWRP, but it was like a different set of files... build.prop was there, I pulled it, edited, and pushed it back, but reboot into system had a DIFFERENT build.prop. Made no sense. I rebooted back into TWRP, mounted system again, found the build.prop there had my changes. It was like there were two versions of /system, one that TWRP gave me and one that the system used. It was maddening, to say the least. Somewhere around 2 or 3am, I started getting sloppy trying to get to the bottom of all this, and I accidentally deleted my system partition and soft bricked the phone.
Thankfully I found this thread:
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
These are stock roms that are flashable in TWRP, but modified in that Dm-verity and force encryption have been disabled in the boot images. With this installed, my phone booted properly again and TWRP had no problem accessing the file system... and thankfully this time around, it was the same /system being mounted as the booted phone, everything actually made sense for a change.
I would strongly recommend flashing that modified stock rom and starting over. Camera2 and everything are running properly and I couldn't be happier.
Click to expand...
Click to collapse
I believe I AM using one of those zips so im not sure how this ended up happening but I'll flash again and see if it helps. Thank you so very much for the reply. Really appreciate it. How's camera2 working for you? You using that modified Google cam with HDR+ or is it just helping the stock camera even more so?

carnivalrejectq said:
I believe I AM using one of those zips so im not sure how this ended up happening but I'll flash again and see if it helps. Thank you so very much for the reply. Really appreciate it. How's camera2 working for you? You using that modified Google cam with HDR+ or is it just helping the stock camera even more so?
Click to expand...
Click to collapse
Stock camera still seems to have sharpening and NR that reduces details. I think it improved some other apps, especially enabling the use of Camera2 on apps that use it (and even allows some apps to record in RAW, which is neat but too much trouble to get working properly). But apps that don't necessarily use Camera2 will still look similar I think, including the stock app.
The Google HDR+ app really makes the hardware here shine, I've got to admit. Its a shame that since I'm running the stock firmware we're stuck with the 32-bit buggy version. It isn't very stable, and the focusing is kind of frustrating when it decides not to cooperate. There's a workaround to use video mode to focus, then switch back to camera mode and lock AE/AF, but even then sometimes I find that on close-focus objects, the focus will shift a bit upon reinit on photo mode before I can lock AF. But when it works... man, it REALLY makes a difference! I went from wanting to return the phone to being rather pleased with it.
Attaching a couple of samples. One of harsh contrasting light by a window, and another in a dark alley outside my office.

Dishe said:
Stock camera still seems to have sharpening and NR that reduces details. I think it improved some other apps, especially enabling the use of Camera2 on apps that use it (and even allows some apps to record in RAW, which is neat but too much trouble to get working properly). But apps that don't necessarily use Camera2 will still look similar I think, including the stock app.
The Google HDR+ app really makes the hardware here shine, I've got to admit. Its a shame that since I'm running the stock firmware we're stuck with the 32-bit buggy version. It isn't very stable, and the focusing is kind of frustrating when it decides not to cooperate. There's a workaround to use video mode to focus, then switch back to camera mode and lock AE/AF, but even then sometimes I find that on close-focus objects, the focus will shift a bit upon reinit on photo mode before I can lock AF. But when it works... man, it REALLY makes a difference! I went from wanting to return the phone to being rather pleased with it.
Attaching a couple of samples. One of harsh contrasting light by a window, and another in a dark alley outside my office.
Click to expand...
Click to collapse
Those do look pretty good. I'm gonna flash one of the zips when I can finally get a chance and try and do this build prop edit again. Any idea which camera apps from the play store use the API?

Off the top of my head I do not. There was a link to a modified one here somewhere which supported RAW in DNG format, but I found it unreliable and a major pain to edit and make look like anything on the phone.
Meanwhile, I found this thread about modifying the in-camera processing to reduce the sharpening and noise reduction:
https://forum.xda-developers.com/showpost.php?p=72246474&postcount=9
Flashed the zip in that post to my stock rom and it cleaned up a lot of apps, including the stock photo app. Cam2 api is necessary for google's HDR plus, but if you just want a better image out of the stock apps, I think that flash is what you need.

Dishe said:
Off the top of my head I do not. There was a link to a modified one here somewhere which supported RAW in DNG format, but I found it unreliable and a major pain to edit and make look like anything on the phone.
Meanwhile, I found this thread about modifying the in-camera processing to reduce the sharpening and noise reduction:
https://forum.xda-developers.com/showpost.php?p=72246474&postcount=9
Flashed the zip in that post to my stock rom and it cleaned up a lot of apps, including the stock photo app. Cam2 api is necessary for google's HDR plus, but if you just want a better image out of the stock apps, I think that flash is what you need.
Click to expand...
Click to collapse
I ended up flashing the stock zip from the post you linked and after that the change to build prop for sure worked and now I'm playing around with one of the Google cams so thanks a lot for sure man. I've been wanting to try it for months while still being able to remain stock. Really appreciate it.

carnivalrejectq said:
I ended up flashing the stock zip from the post you linked and after that the change to build prop for sure worked and now I'm playing around with one of the Google cams so thanks a lot for sure man. I've been wanting to try it for months while still being able to remain stock. Really appreciate it.
Click to expand...
Click to collapse
No problem! Glad it helped! I should probably compile some sort of FAQ or something, lots of information spread across too many threads to make sense of it. But just FYI, I'm pretty sure OTA updates won't work anymore now that you've modified the system.

What have you guys done with your rooted ZTE Blade ZMAX?

After a year since the release, the ZTE Blade Zmax is finally able to be rooted . I want to know, what have you guys done so far with your rooted devices? Any custom tweaks, used a cheat engine, etc? Have you looked into any custom ROMs that may possibly work for this phone? Comment below what you have done so far. Me personally, I tweaked my battery a lot and did a little modification to my kernel. With both magisk and xposed, I have been able to do a lot so far, but I want to do more. That is why I am curious to know cool things that you guys have done so far.

Removed SO much bloat, did the usual magisk modules, used SystemUI Tuner to make some visual changes in the statusbar, and noticed how heavily ZTE modified the system all the way down to the weather app. Currently looking into decompiling and recompiling the systemui to remove the annoying top left carrier wasn't successful in the first attempt so going at it again.

JasonSec said:
Removed SO much bloat, did the usual magisk modules, used SystemUI Tuner to make some visual changes in the statusbar, and noticed how heavily ZTE modified the system all the way down to the weather app. Currently looking into decompiling and recompiling the systemui to remove the annoying top left carrier wasn't successful in the first attempt so going at it again.
Click to expand...
Click to collapse
Interesting. What type of bloatware did you remove? ANy app specific used for that? For the last couple of days, I have been trying to change the boot animation. After may methods and attempts, it serves as no avail, so likewise to you, we both have things we are trying to accomplish. Hopefully, all goes well. Keep me updated on your status.

evtoofly said:
Interesting. What type of bloatware did you remove? ANy app specific used for that? For the last couple of days, I have been trying to change the boot animation. After may methods and attempts, it serves as no avail, so likewise to you, we both have things we are trying to accomplish. Hopefully, all goes well. Keep me updated on your status.
Click to expand...
Click to collapse
Facebook, metrozone, chrome, few other I can't remember. No app just deleted them from /system/(priv-)app via recovery.
For the bootanimation I found a megathread under Android customization, grabbed the zip for the animation I wanted, rebooted to recovery, setenforce 0 via adb, renamed the old bootanimation.zip to old.zip just in case, then pushed the zip to /system/media and rebooted.

JasonSec said:
Facebook, metrozone, chrome, few other I can't remember. No app just deleted them from /system/(priv-)app via recovery.
For the bootanimation I found a megathread under Android customization, grabbed the zip for the animation I wanted, rebooted to recovery, setenforce 0 via adb, renamed the old bootanimation.zip to old.zip just in case, then pushed the zip to /system/media and rebooted.
Click to expand...
Click to collapse
Im going to try that, hopefully, it works. Why did you remove chrome though? Do you find other browsers better? I personally have good experience with chrome. Im trying to do as much tweaks as possible with the device itself, but I done so much already, Im confused on what else there is to do
Update: Bootanimations only work with soft reboots. Im looking for a way to have my custom boot when I hard reboot my phone.

evtoofly said:
Im going to try that, hopefully, it works. Why did you remove chrome though? Do you find other browsers better? I personally have good experience with chrome. Im trying to do as much tweaks as possible with the device itself, but I done so much already, Im confused on what else there is to do
Update: Bootanimations only work with soft reboots. Im looking for a way to have my custom boot when I hard reboot my phone.
Click to expand...
Click to collapse
I find Via much faster and love the customization. Chrome removal that was less about bloat and more about something I'll never use and if I ever do decide to use it or Facebook again it's available in the play store.
Not sure what you mean about boot animations I believe they're loaded and appear each time the system is booted regardless of hard/soft boot (assuming you're not going to recovery mode obviously)

JasonSec said:
I find Via much faster and love the customization. Chrome removal that was less about bloat and more about something I'll never use and if I ever do decide to use it or Facebook again it's available in the play store.
Not sure what you mean about boot animations I believe they're loaded and appear each time the system is booted regardless of hard/soft boot (assuming you're not going to recovery mode obviously)
Click to expand...
Click to collapse
Well, I use the app quick reboot that allows me to boot into recovery, quick restart, or full restart,etc. When I quick reboot, it will show my custom boot animation I downloaded, but when I full reboot, it shows the default metropcs screen which is annoying in my opinion. Maybe because I set my phone in permissive mode using Terminal and not adb
Well anyway, I'm still going to try and fix this because I hard reboot my phone a lot and I just dont wanna see that metro pcs screen anymore. Also, am I the only blade user whose power button does not know how to function I am really about to take this phone apart because my power button seems impossible to work unless I hold it a certain way, and its been like this for a while and I just dont understand why.

Ive spent over a year trying to make a gps spoofing app work on this phone.
Root really didnt help but twrp did.
Moved the app from /data/app to /system/priv-app
then I chmodded the folder and base.apk to 777
additionally I chowned the folder and base.apk to root:root

xxMoon said:
Ive spent over a year trying to make a gps spoofing app work on this phone.
Root really didnt help but twrp did.
Moved the app from /data/app to /system/priv-app
then I chmodded the folder and base.apk to 777
additionally I chowned the folder and base.apk to root:root
Click to expand...
Click to collapse
interesting, I was just thinking about using gps spoof. Did you end up successful in it

Yup

xxMoon said:
Ive spent over a year trying to make a gps spoofing app work on this phone.
Root really didnt help but twrp did.
Moved the app from /data/app to /system/priv-app
then I chmodded the folder and base.apk to 777
additionally I chowned the folder and base.apk to root:root
Click to expand...
Click to collapse
Bro! Not sure if you read the post I made on the other thread, but actually one of my reasons for rooting was achieving a "working" Spoofing method.
Rooting and moving app to system kind of works, but there it a better way and actually works great on this phone.
Just download Smali Patcher 0.0.4.2 from this thread https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053 (Thx to F0mey)) and follow the ADB method (Options 1 and 4),
then just flash the generated magisk module,
install your prefered spoofing app (Im using Ninja's) - **Remember to clone**
set as Mock Location
Everything unchecked on Spoof App (I just leave the distance info one on Ninja's app)
Enjoy!

BlazeMz3 said:
Bro! Not sure if you read the post I made on the other thread, but actually one of my reasons for rooting was achieving a "working" Spoofing method.
Rooting and moving app to system kind of works, but there it a better way and actually works great on this phone.
Just download Smali Patcher 0.0.4.2 from this thread https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053 (Thx to F0mey)) and follow the ADB method (Options 1 and 4),
then just flash the generated magisk module,
install your prefered spoofing app (Im using Ninja's) - **Remember to clone**
set as Mock Location
Everything unchecked on Spoof App (I just leave the distance info one on Ninja's app)
Enjoy!
Click to expand...
Click to collapse
im going to try this. Question, what were your reasons for spoofing? Why did you want to achieve this with root?

xxMoon said:
Ive spent over a year trying to make a gps spoofing app work on this phone.
Root really didnt help but twrp did.
Moved the app from /data/app to /system/priv-app
then I chmodded the folder and base.apk to 777
additionally I chowned the folder and base.apk to root:root
Click to expand...
Click to collapse
Hello could you help me?

Guys might find this easier to use.
(EASY ROOT) Z982 via QFIL or TWRP B20_Modified SYSRW 4/8/19