The included file is a binary that runs a daemon that fixes the lockscreen freeze that happens with dt2w/sw2w kernels. It requires busybox to be installed on your device. If your screen is still unresponsive the first time you attempt to wake your device; shut your screen off, wait a couple seconds, and try again and it will usually work.
The executable will do nothing on its own, so you must either have it start on boot with an init.d script or manually in terminal. It has to be ran as root.
To install the zip boot into recovery and install it using your recovery's standard install method, like installing a kernel or ROM.
To install the binary simply put the file in /system/bin and give it executable permissions
Recovery installer zip:
https://docs.google.com/file/d/0B_hgNZE_j5sVd0Itb1V4RGhhOGc/edit?usp=docslist_api
Binary:
https://docs.google.com/file/d/0B_hgNZE_j5sVLU9wdDEzamFUV0U/edit?usp=docslist_api
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
What this app does? How did you find it?
and after put in system/bin what to do next? how to run it?
Run it from the terminal command line, and it will continue to run in the background.
Its a quick and dirty fix that resets the touch screen driver when the screen is off.
If you copied the file to system bin you should be able to just type "scrfix" in your terminal and it will run in the background until your next reboot.
Alternatively you can just call it in an init.d script to have it start automatically on every boot.
I use SManager , give to scrfix su and boot privs it will work?
I haven't used that app personally, but it sounds like it should. Its normal for the program to seem like it exits because it spawns a child process that runs in the background that is owned by init (PID 1)
Or if you want to launch it manually, you can launch it in Terminal Emulator, but it will need started again on each reboot.
There is now a link to an installer zip for installation from recovery mode that comes with an init.d script included, for anyone using this method, please let me know if you encounter any issues with it. You may need to enable "trust system user" in your su application for it to work. The recovery installer was made with the ZipMe application.
Will this enable DT2W in cm12
Sent from my Moto G using Tapatalk
imranaryan said:
Will this enable DT2W in cm12
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
If you will read the title, you would realize that this mod is a fix for a very common problem faced by dt2w users. If you want dt2w, flash a custom kernel like optimus.
I just tried this on my Moto E 2015 and I ended up flashing a zip I modified when I tried it on my Moto G some time ago. I've found that it does not work when applying dt2w with an app such as Kernel Adiutor. It does work if you apply dt2w with an init.d script, and make it so the scrfix script is ran before the dt2w script. You just have to change the numbers in the beginning of the script name to something like 01 and 02 with the scrfix script having the smaller number.
Thanks for the info, I may upload an updated zip that has the name change to make sure it runs first. Some times too (on my phone atleast) when the screen isn't responsive I'll turn the screen off for 3-5 seconds and try again and it'll usually respond.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
elrod16 said:
Run it from the terminal command line, and it will continue to run in the background.
Its a quick and dirty fix that resets the touch screen driver when the screen is off.
If you copied the file to system bin you should be able to just type "scrfix" in your terminal and it will run in the background until your next reboot.
Alternatively you can just call it in an init.d script to have it start automatically on every boot.
Click to expand...
Click to collapse
i know this is an old forum but I just found it. How can I call it in an init.d script?
Just adding the line
scrfix
to a script.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
elrod16 said:
Just adding the line
scrfix
to a script.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
Click to expand...
Click to collapse
Would this be correct?
#!/system/bin/sh
/system/bin/scrfix
exit 0
Sent from my Moto E 2015 using XDA Labs
V-Droid said:
Would this be correct?
#!/system/bin/sh
/system/bin/scrfix
exit 0
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
Yes, you'll also need another script with this:
#!/system/bin/sh
echo "2" > /sys/android_touch/doubletap2wake
This one needs to run after the previous script so you'll have to name them 98scrfix and 99dt2w. Also make sure their permissions are 0755.
---------- Post added at 08:46 PM ---------- Previous post was at 08:35 PM ----------
amarc78 said:
Yes, you'll also need another script with this:
#!/system/bin/sh
echo "2" > /sys/android_touch/doubletap2wake
This one needs to run after the previous script so you'll have to name them 98scrfix and 99dt2w. Also make sure their permissions are 0755.
---------- Post added at 08:46 PM ---------- Previous post was at 08:35 PM ----------
Click to expand...
Click to collapse
Im not able to change the script permissions, tried root browser but gave me an error. How can I change the permissions?
By the way sorry for the constant questions
Sent from my Moto E 2015 using XDA Labs
V-Droid said:
Im not able to change the script permissions, tried root browser but gave me an error. How can I change the permissions?
By the way sorry for the constant questions
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
Try Root Explorer or ES File manager. As long as your rooted it should work.
amarc78 said:
Try Root Explorer or ES File manager. As long as your rooted it should work.
Click to expand...
Click to collapse
Still no luck, I tried root browser, root explorer and es file explorer all of them gave me the same error.
I also tried moving the file from the external SD card into the internal memory.
By the way, the way I create the scripts is in a .txt file, is this correct?
Sent from my Moto E 2015 using XDA Labs
V-Droid said:
Still no luck, I tried root browser, root explorer and es file explorer
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
You need to put them in /system/etc/initd not on your sdcard.
amarc78 said:
You need to put them in /system/etc/initd not on your sdcard.
Click to expand...
Click to collapse
Thank you very much for all of your help, finally managed to change the permissions :laugh:
Sent from my Moto E 2015 using XDA Labs
Related
Super SU by CF
SuperSU is the Superuser access management tool of the future
Features include:
- Superuser access prompt
- Superuser access logging
- Superuser access notifications
- Per-app notification configuration
- Temporary unroot
- Deep process detection (no more unknowns)
- Works in recovery (no more segfaulting)
- Works when Android isn't properly booted
- Works with non-standard shell locations
- Trusts ADB connection
- Always runs in ghost mode
- Wake on prompt
The Pro version additionally offers:
- OTA survival mode (no guarantees)
- Full color-coded command content logging (input/output/error)
- Per-app logging configuration
- Per-app user override
- PIN protection
Who, What Why ? - said by CF
As you may know, I make a lot of apps that use or require root. I also release rooted kernels. I run into a lot of issues with existing Superuser tools. More importantly, a lot of my users run into these issues as well and then email me about it. So I decided to do something about this. Doesn't mean these were problems you have ever seen, or will ever see.
And thus, I have written - pretty much from scratch - SuperSU. I have taken the su binary command line parameter parsing from Superuser, to make sure that is compatible. Aside from that, it is completely rewritten, because how I wanted to do a number of things was incompatible with the existing codebase.
This is not a stab at ChainsDD, or his skills. He has done great work and will no doubt continue to do so, however, I felt the need for some of these changes, and thus made them. This is an early release, so I expect there will be some unforseen issues somewhere.
From now on, all CF-Root and Mobile ODIN Pro (EverRoot) releases will be built around SuperSU.
Please note that SuperSU is not hardened-security-tested or reviewed, and may be exploitable (... as may other solutions ...).
Install :
Flashable Zip v0.93
Market :
Lite
Pro
Note : Pro is key only, you need to install lite version first.
If you install from market, you will have two superuser, remove older one with system appl remover, or any other application can perform same job.
Remember, if you remove older first without installing newer one, you will lose Root n newer won't run.
One more thing market version will be regular application, so hard reset can delete it. So better install with flashable zip, to make it system application.
Source : http://forum.xda-developers.com/showthread.php?t=1538053
Thanks a lot doc. Gonna give it a try.
---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------
Sorry to say but this belongs to General Section.
Nice one, Dr.Ketan.
Perhaps your fine installation instruction could also include this:
"Superuser (the old one) is a system app and should be removed from /system/app/ folder using Root Explorer, ES Eplorer with root permissions, or similar explorer app. Titanium Backup does not show Superuser in its app list, and therefore cannot remove it."
Otherwise you'll be swamped with Titanium questions.
This is modding
any thing android Mod, should be better place under development.
thogh let's leave it upon moderator..
dr.ketan said:
This is modding
any thing android Mod, should be better place under development.
thogh let's leave it upon moderator..
Click to expand...
Click to collapse
i think it doesnt work if USB debugging is enabled and if it is disabled then it works fine...
grgsiocl said:
i think it doesnt work if USB debugging is enabled and if it is disabled then it works fine...
Click to expand...
Click to collapse
CF says he has fixed that bug in v0.74, and that's the one posted here.
I have no issue with USB debugging ON
Confirmed working fine! Recommended to install via CWM. It will replace the other automatically so you don't have to manually remove it.
Sent from my GT-N7000 using XDA
kopitalk said:
Confirmed working fine! Recommended to install via CWM. It will replace the other automatically so you don't have to manually remove it.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Newbie question here, (sorry) so you don't just download from the market/play store..... open and it will install on it's own?
Sent From my Two Tin Cans & String Device on The Wookie Network
It will install, but not as system application. So it is recommended to flash with CWM. as well you have to remove old manually, if you install from market
dr.ketan said:
It will install, but not as system application. So it is recommended to flash with CWM. as well you have to remove old manually, if you install from market
Click to expand...
Click to collapse
Another newbie question... Is there enough of a difference between superuser & supersu for a newbie to risk mucking up their phone?
Thanks!
EDIT : are there instructions as to how to flash with CWM? SORRY!!
Sent From my Two Tin Cans & String Device on The Wookie Network
Superuser v0.75 has been released.
Changelog:
10.03.2012 - v0.75
- Adjustment to OTA survival (better!)
- Slight speedup in Settings
- Fixed native settings update after temp-re-root
- Clear data no longer clears PIN code
- Layout: Prompt: Grant and Deny switch positions (ICS style)
- Layout: AppDetail: Save and Cancel switched positions (ICS style)
- Layout: Added xlarge PIN layout
http://forum.xda-developers.com/attachment.php?attachmentid=940641&d=1331395344
P.S. Dr.Ketan, when I try to download CWM flashable zip from your 1st post I get a 404.
Ya b'coz link replaced by CF with new version
updated now
dr.ketan said:
Ya b'coz link replaced by CF with new version
updated now
Click to expand...
Click to collapse
even mobile Odin is updated with 2.25
Very Slow Boot Up Following Switch to SuperSU Pro
My Note is running rooted stock ROM with Franco.kernel v6. After installing the SuperSU v.75.zip with CWM and installing the Pro key, and removing Superuser.apk my Note is VERY slow to boot up. It took less than 1 minute immediately prior to SuperSU and now takes 5-6 minutes. It runs wifi and mobile data and sync together EVERY time it boots. It never did this before. It also runs "Media Scanning 6-8 times before it finishes booting.
I'm not complaining, just informing. I realize that this is a new work in progress as posted in the OP post #1. Is anyone else having these issues? If not, any suggestions to correct these problems? I have tried clearing Dalvik and cache partition through CWM app.
Thank you for any help and/or advice.
kraz
krazman325 said:
My Note is running rooted stock ROM with Franco.kernel v6. After installing the SuperSU v.75.zip with CWM and installing the Pro key, and removing Superuser.apk my Note is VERY slow to boot up. It took less than 1 minute immediately prior to SuperSU and now takes 5-6 minutes. It runs wifi and mobile data and sync together EVERY time it boots. It never did this before. It also runs "Media Scanning 6-8 times before it finishes booting.
I'm not complaining, just informing. I realize that this is a new work in progress as posted in the OP post #1. Is anyone else having these issues? If not, any suggestions to correct these problems? I have tried clearing Dalvik and cache partition through CWM app.
Thank you for any help and/or advice.
kraz
Click to expand...
Click to collapse
what you said was true...it slows up booting...but what i did was, in supersu app, i selected grant as default and there is no need for prompt...after that, booting as speed up!
I actually found my own solution as you were posting! Thanks for your help, grgsiocl!!! I did leave default access set to PROMPT though as it will only show the first time until i grant permission.
MY SOLUTION: I unchecked the show Notification Toasts, rebooted and total boot up took 50 seconds!
Sorry for wasting space in this thread!!! Hopefully, anyone else having similar trouble will see this.
kraz
Thanks Doc!flashing now
krazman325 said:
I actually found my own solution as you were posting! Thanks for your help, grgsiocl!!! I did leave default access set to PROMPT though as it will only show the first time until i grant permission.
MY SOLUTION: I unchecked the show Notification Toasts, rebooted and total boot up took 50 seconds!
Click to expand...
Click to collapse
Yeah, this is what CF has to say about it in his original thread:
Chainfire said:
PROTIP:
For extra performance, disable notifications. Logging does not impact performance much.
Click to expand...
Click to collapse
I think it would have been better to just link to chainfires thread rather than repost what he posted.
I have xposed running on my Nexus 5 lollipop 5.0.1.
After downloading and enabling a couple modules my phone is now stuck in a bootloop.
I tried clearing dalvik and cache it didn't help.
Is it possible to disable xposed from recovery?
EDIT: Solved.
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
Click to expand...
Click to collapse
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/xposed/disabled, which causes Xposed to be bypassed as well:
Code:
touch /data/xposed/disabled
Click to expand...
Click to collapse
Didn't work. Still stuck in bootloop.
bseos said:
Didn't work. Still stuck in bootloop.
Click to expand...
Click to collapse
what modules you have activated?
or
mv /system/lib/*.*.orig /system/lib/*.*
mv /system/bin/*.orig /system/bin/*
opssemnik said:
what modules you have activated?
Click to expand...
Click to collapse
It was between two modules. Can't remember the first one but the last one was XInstaller.
Anyway, got it solved using the below method:
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed as well:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
very good
bseos said:
It was between two modules. Can't remember the first one but the last one was XInstaller.
Anyway, got it solved using the below method:
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed as well:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
Click to expand...
Click to collapse
XInstaller seems to be causing a few issues, and I don't think its the app itself but the apps it allows you to install instead. I had the same issue after installing xInstaller. But now that you figured this out maybe I can try a few other apps out like xstana which for somereason refuses to install on lollipop devices...
.Ryker said:
XInstaller seems to be causing a few issues, and I don't think its the app itself but the apps it allows you to install instead. I had the same issue after installing xInstaller. But now that you figured this out maybe I can try a few other apps out like xstana which for somereason refuses to install on lollipop devices...
Click to expand...
Click to collapse
After disabling it I flashed the new xposed-arm-20150308.zip and installed XposedInstaller_3.0-alpha2.apk (I was on alpha1 previously)
Re-enabled xposed (deleted "disabled" file) and all is working fine now.
This thread definitely either needs to be made a sticky, or the contents needs to be in one of the already made sticky threads IMHO
Cheers
//edit
I tried this out on my phone to test (my xposed stuff is working just fine) but it doesn't seem to have disabled xposed at all?
Ex, app settings still functions (set my play store to be at 480 DPI and it's still opening in 480 DPI as it should...)
I made the necessary file you said with fx file manager, not through TWRP recovery though... I don't think it should make a difference though how I made the file, just that it's there.
Maybe my permissions on the file are messed up, I just thought of that..
//edit 2
Yup my perms were messed up, xposed is now disabled for me. Cheers for the info, now I know what to do when some shady looking module backfires on me lol
Thank you so much!!! This worked perfectly on Sprint LG G3 using Candy5 ROM!! Saved me!!
Just to report that the method failed on a Samsung Galaxy S6 Edge (SM-G925F).
I created succesfully the disabled file, but I was still having bootloops.
So I thought I forgot to set the file to 755, but then TWRP told me:
Code:
Updating partition details...
...done
E: Resource (font)-(fixes) failed to load
Kernel does not have support for reading SELinux contexts.
MTP Enabled
Now I hope to fix everything by reflashing the firmware again...
After successfully disabling xposed in order to get the device to boot, how do we reenable it? Because after uninstalling the module which caused the problem the framework is "not active". A reboot did not work.
Nokiacrazi said:
After successfully disabling xposed in order to get the device to boot, how do we reenable it? Because after uninstalling the module which caused the problem the framework is "not active". A reboot did not work.
Click to expand...
Click to collapse
Delete the "disabled" file in the folder op showed
jkyoho said:
Delete the "disabled" file in the folder op showed
Click to expand...
Click to collapse
Silly question but how can I delete it? I tried locating it using HTC file manager and es file explorer but cannot locate it.
Is there a command I can use using terminal emulator or something?
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
Nokiacrazi said:
Silly question but how can I delete it? I tried locating it using HTC file manager and es file explorer but cannot locate it.
Is there a command I can use using terminal emulator or something?
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
You need you use Root explorer or Es file explorer that supported Root and locate to /data/data/de.robv.android.xposed.installer/conf
Method 2:
You can even delete the "disabled" file in recovery by using file management, if you are using TWRP. Same as previous method, just locate to /data/data/de.robv.android.xposed.installer/conf
jkyoho said:
You need you use Root explorer or Es file explorer that supported Root and locate to /data/data/de.robv.android.xposed.installer/conf
Method 2:
You can even delete the "disabled" file in recovery by using file management, if you are using TWRP. Same as previous method, just locate to /data/data/de.robv.android.xposed.installer/conf
Click to expand...
Click to collapse
Thanks, method 2 worked a treat.
For some reason, even though I have root access, it wasn't showing in either root explorer or es file explorer, however, when looking through TWRP file management was all there.
jkyoho said:
Delete the "disabled" file in the folder op showed
Click to expand...
Click to collapse
can you please explain the process.
i entered the twrp and advanced and terminal command and went through the shown path yet i didnt see the file "disabled"
he has said to create a file; how could i create a file??
please explain the process...
cybercop007 said:
can you please explain the process.
i entered the twrp and advanced and terminal command and went through the shown path yet i didnt see the file "disabled"
he has said to create a file; how could i create a file??
please explain the process...
Click to expand...
Click to collapse
If you can't normally boot to system, boot to recovery(twrp or some other custom recovery which has file management function)
Try copy a small file like host or something, paste it the that /data/data/dev.*****installer/conf folder and rename it "disabled".
flashable zip´s
starbase64 said:
flashable zip´s
Click to expand...
Click to collapse
these will be very good to have! thank you!
starbase64 said:
flashable zip´s
Click to expand...
Click to collapse
Thank you!!!
**I did not write these scripts, just updated the flashable zip for our x86 Asus phones**
**All work done by @Paget96**
ORIGINAL Mod Thread here : http://forum.xda-developers.com/android/software-hacking/tweak-l-speed-v1-0-02-02-2015-t3020138
@Paget96 has added an x86 version to the original thread with the (more appropriate) fixes!! Go discuss there!
Big thanks to him. Use the v2.4 Test3 or greater "x86" file
Reqs:
1) Need root
2) Need Custom recovery (TWRP)
3) Need kernel with init.d support (like @TheSSJ 's here: http://forum.xda-developers.com/zenfone2/development/project-t-custom-kernel-zenfone-2-t3150822)
** Use v44 or greater for proper init.d support
Download zip from the original thread
and flash in recovery.
Then look at the original thread for config options while you're in there
Added the Emergency Uninstaller zip as well. (i think you still need to use this version, until an x86 version is up there too)
Ch-Ch-Ch-Ch-Changes
Jul 23 2015: OG thread updated by dev. Updated flashing instructions in OP (mods can probably lock this thread)
Jul 15 2015: Fixed script to properly set perms on /system/bin/LS; Added Emergency Uninstaller zip
Jul 14 2015: Initial upload. Needed to use the update-binary from Asus to work with our x86 architecture and replace all the set_perms with set_metadata's. Apparently the update-binaries from Asus don't include set_perms
I would have expected that some parts of my kernel would fight against this tweak, nice to see that it seems to work
Yean I don't know that some of the governor stuff is working 100%, still messing around with it .
Thanks man Been using TheSSJ kernel with this pack of tweak. Its awesome Thanks to both of you
Added in index, thanks for updating the mod!
taylor.fowler said:
@aziz07 Here you go.
Needed to use the update-binary from Asus to work with our x86 architecture and replace all the set_perms with set_metadata's. Apparently the update-binaries from Asus don't include set_perms
Click to expand...
Click to collapse
Thanks! Working A++
Edit: I tried running the script from terminal with no luck. I have to cleanup the alpha version first with the provided uninstaller by Paget96. Its a great idea to have the uninstaller zip working with x86.
++Uninstaller patched, permssions fixed, kudos @taylor.fowler
Need help can't get to run in terminal
Sent from my ASUS_Z00AD using Tapatalk
taylor.fowler said:
@aziz07 Here you go.
Needed to use the update-binary from Asus to work with our x86 architecture and replace all the set_perms with set_metadata's. Apparently the update-binaries from Asus don't include set_perms
Click to expand...
Click to collapse
how can i do that because not work for me
Have u guys tried with Kernel Adiutor?
su
LS > permission denied
selinux already permissive
chobztopz said:
su
LS > permission denied
selinux already permissive
Click to expand...
Click to collapse
I've got it too
The permission for LS file in system/bin is wrong. It should be 0755 (rwx rx rx) then it will done on terminal emulator
lordpipa said:
Have u guys tried with Kernel Adiutor?
Click to expand...
Click to collapse
I am using that.. But y u asked?
And guys only cleaner works it seems, he added logs for all option thankfully and only cleaner having log, others are blank, I can't run the options of LS..
mustatir said:
The permission for LS file in system/bin is wrong. It should be 0755 (rwx rx rx) then it will done on terminal emulator
Click to expand...
Click to collapse
Yep thanks, OP can you edit the updater script please...
After that script enable also same result, no log entered in those files..
Kernel samepage merging didn't came, no swap.. kernel auditor can enable kernel samepage merging even without this script. .. .
ansebovi said:
I am using that.. But y u asked?
And guys only cleaner works it seems, he added logs for all option thankfully and only cleaner having log, others are blank, I can't run the options of LS..
Yep thanks, OP can you edit the updater script please...
After that script enable also same result, no log entered in those files..
Kernel samepage merging didn't came, no swap.. kernel auditor can enable kernel samepage merging even without this script. .. .
Click to expand...
Click to collapse
Hrmph. I must have Ul'd the wrong version. I had the same issue. Will re-up in a couple hours.
@ansebovi cause u can use it for some of the init scripts.
Hmm, mine does all have logs. Yep, I had to set LS permissions to all in /system/bin folder. I think it might be because I still have the old alpha version files and I can't flash the uninstaller as it needs the x86 code.
Edit: ++Uninstaller patched, permssions fixed, kudos @taylor.fowler
Checked the updater-script. All functions are already available in TWRP itself, so normally you don't even need the updater-binary in the zip file, maybe this makes also the uninstaller work if you just delete the updater-binary from the zip file
TheSSJ said:
Checked the updater-script. All functions are already available in TWRP itself, so normally you don't even need the updater-binary in the zip file, maybe this makes also the uninstaller work if you just delete the updater-binary from the zip file
Click to expand...
Click to collapse
OK, so I fixed the updater-script (and found another error with setting the permissions on init.d). Apparently I had changed them to 0775 instead of 0755 :silly:
Also added the emergency uninstaller script too.
@TheSSJ I dont think that's how flashable zips work, but i tried anyhow. No dice...
taylor.fowler said:
@TheSSJ I dont think that's how flashable zips work, but i tried anyhow. No dice...
Click to expand...
Click to collapse
Bummer...was convinced this would work...twrp code at least shows that it executes updater-binary if present,otherwise it interprets the script itself...
Sorry!
I've researched and tried every method to get AdAway to work. I uninstalled some system apps which allowed me to install it but I cannot get past that because of the S-off warning screen.
I am rooted and bootloader is unlocked. Ive attatched a screenshot of my kernel etc
Do you have a folder called init.d in system/etc?
I have installed Adaway on at least 6 different Marshmellow ROM's with no issue.
Switch ROM and Kernels and see what happens.
Just FYI, this is a development area. You will have more luck posting in the Q&A section.
You seem to be using system less root, that's probably the issue. In the adaway thread there is a zip that must be flashed if you're using system less root.
Also questions belong in the Q&A section not dev section. I've reported the thread, a mod should move it but just letting you know for next time.
miguelito18 said:
Do you have a folder called init.d in system/etc?
Click to expand...
Click to collapse
No i do not
Mike02z said:
I have installed Adaway on at least 6 different Marshmellow ROM's with no issue.
Switch ROM and Kernels and see what happens.
Click to expand...
Click to collapse
Do you have a suggestion on a kernel? And id like to stay stock on the ROM if possible
Mike02z said:
Just FYI, this is a development area. You will have more luck posting in the Q&A section.
Click to expand...
Click to collapse
Ya sorry, i was tryng to post it quick on my phone and didnt look at all the options as to where the best place to post would be
Khizar said:
You seem to be using system less root, that's probably the issue. In the adaway thread there is a zip that must be flashed if you're using system less root.
Also questions belong in the Q&A section not dev section. I've reported the thread, a mod should move it but just letting you know for next time.
Click to expand...
Click to collapse
What is system less root if i may ask? and ill look for that zip you mentioned
*update* installed that zip. attempted to install and get the same error about s-off
@trbomp5 Adaway working flawless on systemless (2.66) rooted stock rom, @ OP do you have busybox installed?
Quote: *update* installed that zip. attempted to install and get the same error about s-off
What do you mean with s-off?
gee2012 said:
@trbomp5 Adaway working flawless on systemless (2.66) rooted stock rom, @ OP do you have busybox installed?
Quote: *update* installed that zip. attempted to install and get the same error about s-off
What do you mean with s-off?
Click to expand...
Click to collapse
Yes busybox is installed.
and if you look at the op youll see the screenshots where i get the s-off error message
trbomp5 said:
Yes busybox is installed.
and if you look at the op youll see the screenshots where i get the s-off error message
Click to expand...
Click to collapse
Symlink to /data/data/hosts in settings.
gee2012 said:
Symlink to /data/data/hosts in settings.
Click to expand...
Click to collapse
yes.
its seems fine till it says symlink missing. then when i click yes to create i get the symlink creation failed. like in the screenshot.
just tried it again
trbomp5 said:
yes.
its seems fine till it says symlink missing. then when i click yes to create i get the symlink creation failed. like in the screenshot.
just tried it again
Click to expand...
Click to collapse
Clear all Adaway data in /settings/apps/ and try again. It should work fine as it does for me. What rom/kernel/recovery are you running?
gee2012 said:
Clear all Adaway data in /settings/apps/ and try again. It should work fine as it does for me. What rom/kernel/recovery are you running?
Click to expand...
Click to collapse
cleared data and tried again same results.
stock rom, unlocked bootloader, kernel is 3.10.40-ElementalX-N6-3.00, twrp 2.8.7.1
Universal init.d install it from play store and follow instructions
miguelito18 said:
Universal init.d install it from play store and follow instructions
Click to expand...
Click to collapse
downloaded it, installed fine. Opened it, granted it SU and then it says "unfortunately, Universal init.d has stopped"
trbomp5 said:
downloaded it, installed fine. Opened it, granted it SU and then it says "unfortunately, Universal init.d has stopped"
Click to expand...
Click to collapse
I don't have an init.d folder as I run the stock kernel. There must be another problem.
I was facing the same problem, for every one trying to get adaway to work on android 6.0.1, follow these steps
Boot to TWRP recovery -> Mount system
adb shell
cd system
cd etc
rm hosts
ln -s /data/data/hosts /system/etc/hosts
In AdAway -> Settings -> hosts file to use is /data/data/hosts
gee2012 said:
I don't have an init.d folder as I run the stock kernel. There must be another problem.
Click to expand...
Click to collapse
ill find the guide i used to root and link it here to see if anyone see's a problem there
http://nexus5.wonderhowto.com/how-to/root-nexus-device-running-android-6-0-marshmallow-0165131/
Yasharkhan said:
I was facing the same problem, for every one trying to get adaway to work on android 6.0.1, follow these steps
Boot to TWRP recovery -> Mount system
adb shell
cd system
cd etc
rm hosts
ln -s /data/data/hosts /system/etc/hosts
In AdAway -> Settings -> hosts file to use is /data/data/hosts
Click to expand...
Click to collapse
just to clearify, those steps are all done in recovery? And im not the best at ADB on the computer, used to odin on samsung the last 3 years
any way i can get you to step by step these with all i need to do?
trbomp5 said:
ill find the guide i used to root and link it here to see if anyone see's a problem there
http://nexus5.wonderhowto.com/how-to/root-nexus-device-running-android-6-0-marshmallow-0165131/
Click to expand...
Click to collapse
Look in the stickies thread in general for how to root.
Usually what i do is:
Flash or boot into TWRP
Flash superuserSU
Install BusyBox
That's it as i use the stock rom, kernel and recovery. I just need root.
---------- Post added at 01:59 AM ---------- Previous post was at 01:57 AM ----------
trbomp5 said:
just to clearify, those steps are all done in recovery? And im not the best at ADB on the computer, used to odin on samsung the last 3 years
Click to expand...
Click to collapse
No, when the device is turned on.
Please note, this requires SELinux Permissive (included init.d script/instructions for PHH). It will not work on Enforcing, even with supolicy (I've tried. If anyone has an idea how to get it working with "soundserver" and setting supolicy "read write execute", please let me know)
Setting SELinux to Permissive is a security risk.
ViPER4Android for Mate 9
Slightly modified guitardedhero script.
Contains "Kernel" and "Profile" for V4A from auras76 kang rom
Note:
The following files are backed up automatically so you can easily revert with the removal script:
/system/lib/soundfx/libeffectproxy.so -> /system/lib/soundfx/libeffectproxy.so.bak
/system/etc/audio_effects.conf -> /system/etc/audio_effects.conf.bak
/vendor/etc/audio_effects.conf -> /vendor/etc/audio_effects.conf.bak
If those .bak files are not found the removal script won't run (to prevent running it without V4A installed, it would simply just remove the files leaving you with no files at all.)
It does not edit audio_policy.conf as it doesn't have the deep_buffer section in it, so no point in having it edited.
Requirements:
SuperRoot/SuperSU (No verity is probably needed as we're modifying both /system and /vendor)
A way to set SELinux to Permissive (SuperSU init.d/phh 'su --init' or SELinuxToggler, see 'Alternative'.)
If you're on Magisk use the V4A module instead
For SuperSU
If you use the one posted above
Simply flash the zip in TWRP and you should be good to go. It copies the 00selinux script directly to /system/etc/init.d/ and runs at boot so you'll have SELinux set to Permissive after flashing.
For PHH su
Flash the zip in TWRP, boot up fully.
Now open a terminal and issue the command
Code:
su --init /system/etc/init.d/00selinux
Then reboot.
To remove the phh init use 'su --init !/system/etc/init.d/00selinux'.
For Magisk
Search for Viper4Android in the Downloads section in Magisk Manager, it's a module so no need to download anything in this thread
Alternative:
(You still need root for this but no init script.)
SELinuxSwitch by @Ibuprophen
Download:
ViPER4Android 2.5.0.5
Dropbox Mirror
Removal script download:
Removal script
Removal script Dropbox Mirror
Thanks to V4A team,
guitardedhero for his script,
auras76 for the profiles/makers of said profiles,
Ibuprofen for The SELinux Switch.
@ante0 bro thanks for porting it... have a question, we have to mount system in terminal for writting in system partition,,, can i use init to mount system rw for all time so that i dont need to give command everytime
HassanMirza01 said:
@ante0 bro thanks for porting it... have a question, we have to mount system in terminal for writting in system partition,,, can i use init to mount system rw for all time so that i dont need to give command everytime
Click to expand...
Click to collapse
Yes, if you use supersu, make a script in /system/etc/init.d/
Code:
#!/system/bin/sh
mount -o rw,remount /system
Make sure it runs after any other scripts if they remount system to read only. Scripts are loaded in order, so name it accordingly.
If you use phh, place script where you want and from a terminal
Code:
su --init /path/to/script
I wanna put all this in my Kernel... Or boot.img...
I have root in my kernel using phh superuser... I dont want to add anything in system by myself, i want that a zip should do it... Will be best if kernel did all this... In MM, we dont need to do rw ourself, in N we needed...
Also, am not a dev, just a pro member, know how to edit and understand commands etc...
May I ask whats the difference between this and Viper4Arise.
HassanMirza01 said:
I wanna put all this in my Kernel... Or boot.img...
I have root in my kernel using phh superuser... I dont want to add anything in system by myself, i want that a zip should do it... Will be best if kernel did all this... In MM, we dont need to do rw ourself, in N we needed...
Also, am not a dev, just a pro member, know how to edit and understand commands etc...
Click to expand...
Click to collapse
I sent you a pm instead
ante0 said:
I sent you a pm instead
Click to expand...
Click to collapse
Sure bro... Am waiting... And i have somehow injected phh superuser r275 in boot.img... I will be thankful if u tell me the whole correct procedure to inject files of superuser zip in boot.img.... By flashing superuser r275 on stock boot, we can have root but on that root, titanium like apps didnot work :/
SlyUK said:
May I ask whats the difference between this and Viper4Arise.
Click to expand...
Click to collapse
Arise is based off of V4A, but with their own audio effects and a modified V4A app.
https://www.reddit.com/r/androidapps/comments/5dpvcz/slug/da6ux9k
SlyUK said:
May I ask whats the difference between this and Viper4Arise.
Click to expand...
Click to collapse
It's just a skin difference. Viper4Arise is themed by an arise member. The only difference is the theme.
ante0 said:
Arise is based off of V4A, but with their own audio effects and a modified V4A app.
https://www.reddit.com/r/androidapps/comments/5dpvcz/slug/da6ux9k
Click to expand...
Click to collapse
Hello,
Will V4A work on P9, P9 plus and P9 lite if we flash those files?
Coolyou said:
Hello,
Will V4A work on P9, P9 plus and P9 lite if we flash those files?
Click to expand...
Click to collapse
I don't know. But I don't see why it wouldn't.
Backup system and try.
You'll have to use the phh init script though as I don't think supersu works with P9 on emui5?
Edit: actually, if your audio_effects.conf file is not in /system/etc/ or /vendor/etc/ the script needs to be modified. And if your audio_policy.conf contains the deep_buffer section.
You guys can use this app for switching SELinux to Permissive - https://forum.xda-developers.com/android/apps-games/app-selinuxtoggler-t3574688
It was featured a few days back on XDA blog, hope it will help the users.
DJBhardwaj said:
You guys can use this app for switching SELinux to Permissive - https://forum.xda-developers.com/android/apps-games/app-selinuxtoggler-t3574688
It was featured a few days back on XDA blog, hope it will help the users.
Click to expand...
Click to collapse
Oh, he finally released it
I'll update OP, thanks for heads-up.
Works like a charm, thanks
hi..I'm on aura's rom. and I can't install drivers. can you please teach me how can I make it work..thanks
s2pfie said:
hi..I'm on aura's rom. and I can't install drivers. can you please teach me how can I make it work..thanks
Click to expand...
Click to collapse
assuming everything else but the driver is installed,
simply download Viper4android_2.5.0.5_mate9.zip, extract.
go to customize/lib, rename libv4a_fx_jb_NEON.so to libv4a_fx_jb_ics.so
copy it to your phone.
Use a root file manager and copy and paste to /system/lib/soundfx/libv4a_fx_jb_ics.so.
And set permissions of that file to 0644 (RW-R--R--).
Then reboot and open up viper4android again and see if still complains.
If it doesn't, go to "hamburger" menu in V4A and tap on Driver Status, it should say Status: Normal. If it says abnormal something else is wrong.
ante0 said:
assuming everything else but the driver is installed,
simply download Viper4android_2.5.0.5_mate9.zip, extract.
go to customize/lib, rename libv4a_fx_jb_NEON.so to libv4a_fx_jb_ics.so
copy it to your phone.
Use a root file manager and copy and paste to /system/lib/soundfx/libv4a_fx_jb_ics.so.
And set permissions of that file to 0644 (RW-R--R--).
Then reboot and open up viper4android again and see if still complains.
If it doesn't, go to "hamburger" menu in V4A and tap on Driver Status, it should say Status: Normal. If it says abnormal something else is wrong.
Click to expand...
Click to collapse
thanks bro but still an error occurred..still abnormal
update:
just flashed your zip now its normal..thank you
@ante0, I just wanted to give you a quick heads up...
There's a new app (currently being beta tested) that will supercede/replace The SELinux Toggler....
It's a new app called "The SELinux Switch". Though, it will look like "The SELinux Toggler" but, I had to recreate, pretty much, the whole app.
The reason i had to do this is, primarily, to completely sever it from the older package name (or Installation Directory) that was also being used by the "SELinuxModeChanger" app.
I also had made some minor enhancements and a few compatibility improvements but, there's still some more improvements to be made.
In addition, the app has been passing the beta testing extremely well (thankfully after about 6 +/- months into it) and it should be released soon but, when the app has completed the beta testing and, ready for its debut, it will be released under a whole new thread.
Thank you all for your time, understanding and, especially, your support for my development.
Please let me know if you have any questions or concerns.
______________
PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
Has anybody used the ARISE aroma installer (twrp flashable zip)? I've used it on a few other devices, coming to the M9 from a Le Pro 3 and it works nice and easy and patches selinux permanently. It seems the way Huawei does things is much different though, so I'd be suprised if it works as easily as on other phones.
In the end, it's just installing 2.5.0.5 anyway with a few other tweaks and a whole bunch of IRS response profiles. So that part's not very different.
Just a quick heads-up @ante0...
The SELinux Toggler has now Officially been Discontinued for the launching of the new app...
[APP][TOOL][4.2+][OFFICIAL]The SELinux Switch by Ibuprophen
Those of you who currently has The SELinux Toggler, and want to switch to The SELinux Switch, please be sure to read the OP for instructions.
Thank you ALL!
______________
PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.