Related
I have a Verizon GT that I may have to exchange. Since there is no real return to defaults capability and no officially available ROM image to reload, I may need to remove some of the things I have installed. So far I have rooted it and installed BusyBox to facilitate running VPN. I know how to unroot it, but how do I remove BusyBox? The installer does not seem to have an uninstall option. Thoughts?
First of all find intallation directory and then remove (delete) it using Root Explorer. If you know how did you install it you can look at the script and find it.
Typically Busybox is installed in /system/xbin
I think you can leave it as is because nobody will look at your Tab. It will be reflashed and retested because they realize that it was used.
Can you not find it in the market and while in the market select Uninstall?
Digiguest said:
Can you not find it in the market and while in the market select Uninstall?
Click to expand...
Click to collapse
Tried it. That just uninstalls the installer, not BusyBox itself
busy box
yes, all you can do is uninstall busy box on apps manager.also cannot delete or move it when accessing by root explorer. Also when rooting by superone click it prompts that if you want to install busybox, so did it..there are two versions of busybox in the market.pls help regarding with this problem.any one
Okay so I have tried all the options on their development page on G+ but there seems to be a lot of arrogance from the devs about users with issues and not doing research even though following the instructions leads to nothing.
- Im rooted via CF's systemless root method
- I have TWRP 2.8.7.2 installed and working
- Busybox is installed in /system/xbin
- I have the correct Vendor image for my device
- Stock ROM 6.0.1
I use busy box on a rail to check its correctly installed and double check with a file explorer but still no themes will apply.
EDIT : Solved it - DON'T USE BUSYBOX ON RAILS ! for some reason it does not work with Layers correctly!
1. Uninstall any busy box installs
2. Reboot
3. Install busybox app from the play store and select /system/binx as the install location
4. Reboot
5. Profit
Anyone have any ideas to get this working ?
I'll give it a try had nothing but issues trying to use layers, currently got busybox on rails installed but as you've mentioned can't get it working, I'll try as you've suggested thanks
Sent from my Nexus 6P using Tapatalk
Spot on
hutzdani said:
Okay so I have tried all the options on their development page on G+ but there seems to be a lot of arrogance from the devs about users with issues and not doing research even though following the instructions leads to nothing.
- Im rooted via CF's systemless root method
- I have TWRP 2.8.7.2 installed and working
- Busybox is installed in /system/xbin
- I have the correct Vendor image for my device
- Stock ROM 6.0.1
I use busy box on a rail to check its correctly installed and double check with a file explorer but still no themes will apply.
EDIT : Solved it - DON'T USE BUSYBOX ON RAILS ! for some reason it does not work with Layers correctly!
1. Uninstall any busy box installs
2. Reboot
3. Install busybox app from the play store and select /system/binx as the install location
4. Reboot
5. Profit
Anyone have any ideas to get this working ?
Click to expand...
Click to collapse
Thank you so much for discovering this, I was going crazy why I couldn't create the overlay folder under vendor, this is the solution, to everyone who sees this, don't listen to whoever says busybox on rails is the way to go...
If you have supersu 2.65 and install busybox to /su/xbin then it will also work.
I have superuser 2.65 and following your instructions finally have layers working, thanks dude
Sent from my Nexus 6P using Tapatalk
Perfect, thank you
Sent from my Nexus 6P using Tapatalk
hutzdani said:
Okay so I have tried all the options on their development page on G+ but there seems to be a lot of arrogance from the devs about users with issues and not doing research even though following the instructions leads to nothing.
- Im rooted via CF's systemless root method
- I have TWRP 2.8.7.2 installed and working
- Busybox is installed in /system/xbin
- I have the correct Vendor image for my device
- Stock ROM 6.0.1
I use busy box on a rail to check its correctly installed and double check with a file explorer but still no themes will apply.
EDIT : Solved it - DON'T USE BUSYBOX ON RAILS ! for some reason it does not work with Layers correctly!
1. Uninstall any busy box installs
2. Reboot
3. Install busybox app from the play store and select /system/binx as the install location
4. Reboot
5. Profit
Anyone have any ideas to get this working ?
Click to expand...
Click to collapse
For me with su 2.65 and busybox on rails, things are working. However, not as expected. Sometime even I change some overlay it won't apply. Sometime the dialer and other fonts won't be visible at all. May be I should try ur method. Thanks.
Sent from my Nexus 6P using Tapatalk
This method will defeat the purpose of systemless root though, right? So Android Pay and Good for Enterprise will cease to work because /system had been edited?
Hello, I'm on the latest 6.0.1 stock. I've used Nexus Root Toolkit to unlock my bootloader, root (SuperSU), and flash TWRP. I flashed Xposed using the Xposed installer. Now I'm looking to get AdAway up and running. I've done some searching and I see some conflicting reports about whether this needs to be done systemless, and how to get it working. Stuff I've heard is:
1. Just install the apk from XDA and install normally, update hosts, and you're good.
2. Install apk, use a program (like Titanium Backup) to make it a system app, update hosts, done.
3. Install apk, flash some sort of AdAway package in TWRP, update hosts, done.
4. Install apk, do some adb process to create a symlink of some sort, update hosts, done.
5. I haven't heard anyone really mention it, but in Preferences I see an option to "Enable systemless mode" which I haven't seen anyone really mention.
Can someone tell me which way I need to use, please?
>>> I also saw someone say that I need to use a file explorer after updating hosts to manually switch the permissions of the hosts file, in order to improve performance. Can anyone tell me if this is accurate, and if so how to do it?
Thanks!
kwest12 said:
Hello, I'm on the latest 6.0.1 stock. I've used Nexus Root Toolkit to unlock my bootloader, root (SuperSU), and flash TWRP. I flashed Xposed using the Xposed installer. Now I'm looking to get AdAway up and running. I've done some searching and I see some conflicting reports about whether this needs to be done systemless, and how to get it working. Stuff I've heard is:
1. Just install the apk from XDA and install normally, update hosts, and you're good.
2. Install apk, use a program (like Titanium Backup) to make it a system app, update hosts, done.
3. Install apk, flash some sort of AdAway package in TWRP, update hosts, done.
4. Install apk, do some adb process to create a symlink of some sort, update hosts, done.
5. I haven't heard anyone really mention it, but in Preferences I see an option to "Enable systemless mode" which I haven't seen anyone really mention.
Can someone tell me which way I need to use, please?
>>> I also saw someone say that I need to use a file explorer after updating hosts to manually switch the permissions of the hosts file, in order to improve performance. Can anyone tell me if this is accurate, and if so how to do it?
Thanks!
Click to expand...
Click to collapse
Hello... Just allow SU permission, tic "enable systemless mode" in preferences if you use systemless Root. Tap on "disable" next to the red cross and let it download the new host. When prompted, reboot. Done...
Never seen anything about setting extra permissions... I don't read the XDA thread anyway and downloaded the app from here: https://f-droid.org/repository/browse/?fdid=org.adaway
Cheers...
Hey everyone! I seem to have found put together 3 methods of installing/bypassing the V4A App on android. These methods include:
Regular Installation, and 2 Error bypasses/fixes.
If you get the error "superuser manager doesn't allow app to access su or you don't have root at all. fix this to use this selinuxmodechanger!", then you've come to the right place.
Requirements: ROOT, (maybe) TWRP (or anything you can flash the zip onto your phone with. With this tutorial I'll be using TWRP.)
If you don't have TWRP, here's the link to that \\ https://twrp.me/Devices/
Type in/select your device, click download, and flash it to your phone.
====================================================================================
Regular installation:
1.) Download V4A from Google Play Store \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
2.) Open, and grant root permission.
3.) Install drivers, and reboot phone. DONE!
==================================================================================================
V4A SuperSU Manager Error:
1.) Download V4A from Google Play Store (the newest one) \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
Open it, grant permissions, click "install drivers" <- just get through the driver menu. This is a troubleshoot test. If it fails, keep going on with the tutorial. If not, You're A-Okay.
2.) Download V4A Flashable ZIP from here \\ https://drive.google.com/file/d/0By-5wpCgi7OHMjFZRU1PYXljbDQ/view
Drag and drop from your computer onto your phone in your "Downloads" folder.
3.) Open TWRP and click "Install" and navigate to your "Downloads" folder where you Installed the V4A Flashable ZIP (Viper4AndroidMM_v2.4.0.1.zip)
Install the ZIP in TWRP, and reboot.
4.) Open your apps/app menu, navigate to the new (it's an older version, but it's newly installed) V4A. It should be a purple logo instead of a blue logo. At this point in the tutorial, you should have both the Google Play Store APK, and the TWRP Flashed APK. Open the PURPLE V4A, and Install drivers now.
5.) Reboot phone, go to the NEW (blue logo) V4A, and install drivers on that one too.
The rest is clean-up. You may now delete the older version of V4A (purple logo).
========================================================
Bypass/fix #2, The SELinuxModeChanger issue:
1.) Download V4A (newest version) from \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
2.) (Grant root access) Attempt to install drivers. If this succeeds, then Idk why you're still here.
3.) Download SELinuxModeChanger APK from \\ http://forum.xda-developers.com/devdb/project/dl/?id=12506
4.) Open it, grant root access, and click "Permissive".
5.) Re-boot phone, and open V4A when done.
6.) Install drivers!
Sources/credit go to:
https://forum.xda-developers.com/showthread.php?t=2524485
^ SELinuxModeChanger
https://forum.xda-developers.com/lg-g3/themes-apps/app-viper4android-v2-4-0-1-lg-g3-t3311403
^ Driver install failure/ Disc I/O error/"superuser manager doesn't allow app to access su or you don't have root at all. fix this to use this selinuxmodechanger!" error
https://twrp.me/about/
^ Team Win
https://forum.xda-developers.com/member.php?u=7249915
^ Me, I contributed very small amounts, that's why I'm last (I guess I contributed some common sense .. ?)
what if you already have permissive kernel , and still get i\o error during driver install?
using android auto 7.1.1 head unit.
masri1987 said:
what if you already have permissive kernel , and still get i\o error during driver install?
using android auto 7.1.1 head unit.
Click to expand...
Click to collapse
Follow this guide for installation if already permissive
https://forum.xda-developers.com/moto-x-2014/themes-apps/mod-viper-4-android-oreo-tested-t3700287
For i\o error you should do step No.8
zahidm said:
Follow this guide for installation if already permissive
https://forum.xda-developers.com/moto-x-2014/themes-apps/mod-viper-4-android-oreo-tested-t3700287
For i\o error you should do step No.8
Click to expand...
Click to collapse
my head unit doesn't have vendor/etc or the audio effects configuration file....
Thanks
I had the Viper.apk from their website and the Google play version loaded also and I was getting the I/O error when trying to load the driver and the Google Play version didn't work at all. I did try to load SuperSU and busybox before attempting to load the driver again and it still didn't work. I don't know about permissive kernel, I'm running Resurrection ROM on a Rooted Note 3. The way I got this to work was to uninstalled the V4A Viper APK version that I had retrieved and loaded from their website. Next I booted into TWRP recovery and installed the V4A Flashable ZIP from the link that I found here. Next I ran the flashed version and granted SU permissions when asked during the install driver process. The driver finally loaded and bingo it works now.
Viper4android
Hi I have installed viper4android fx but in Driver status it shows no processing my phone(samsung j700f) is rooted with Supersu and using Wycked custom Rom nougat based I have done All the method like rename audio_effect.conf file but nothing to happened. All are waste of time.i spend too much time on xda site for solution but not found any solution...can anybody help me please?...Sorry for my bad English.. Thanx in Advance
Banty448 said:
Hi I have installed viper4android fx but in Driver status it shows no processing my phone(samsung j700f) is rooted with Supersu and using Wycked custom Rom nougat based I have done All the method like rename audio_effect.conf file but nothing to happened. All are waste of time.i spend too much time on xda site for solution but not found any solution...can anybody help me please?...Sorry for my bad English.. Thanx in Advance
Click to expand...
Click to collapse
Follow simple steps, first Rename file.bak
Then flash V4A,
Than open V4a it will ask to install driver
Just hit install and wait, it freez for sometime.. and it will say done
Reboot
zahidm said:
Follow simple steps, first Rename file.bak
Then flash V4A,
Than open V4a it will ask to install driver
Just hit install and wait, it freez for sometime.. and it will say done
Reboot
Click to expand...
Click to collapse
But I did it already many times but U tell me little bit different you said rename it before flashing but I did it After flashing .I flashed the zip file and after that rename than open Viper4android fx...ok I will try it...Thanx
Banty448 said:
But I did it already many times but U tell me little bit different you said rename it before flashing but I did it After flashing .I flashed the zip file and after that rename than open Viper4android fx...ok I will try it...Thanx
Click to expand...
Click to collapse
You have to rename file before opening V4A app for the first time, now you rename it before or after flashing no matter,
Sent from my Nokia 5.1 Plus using Tapatalk
0
zahidm said:
You have to rename file before opening V4A app for the first time, now you rename it before or after flashing no matter,
Sent from my Nokia 5.1 Plus using Tapatalk
Click to expand...
Click to collapse
I already told u that I did it before opening the v4a
Banty448 said:
0
I already told u that I did it before opening the v4a
Click to expand...
Click to collapse
The error you are saying it never been seen, please try again
Sent from my Nokia 5.1 Plus using Tapatalk
zahidm said:
The error you are saying it never been seen, please try again
Sent from my Nokia 5.1 Plus using Tapatalk
Click to expand...
Click to collapse
I have done it many times but nothing happened. I tired to install this so now I install Devinebeats it's working fine.Thanx for us replies?
Banty448 said:
I have done it many times but nothing happened. I tired to install this so now I install Devinebeats it's working fine.Thanx for us replies[emoji106]
Click to expand...
Click to collapse
You didn't followed this guide?
https://forum.xda-developers.com/mo...od-viper-4-android-oreo-tested-t3700287/page2
Sent from my Nokia 5.1 Plus using Tapatalk
When I install drivers for ViPER4Android FX I get "Driver installed, please reboot your device." and when I reboot, I'm asked to install drivers again. Did anyone figure out how to successfully install these drivers? I saw fixed around the forum, but they don't seem to work for me.
My phone huawei p10 lite rom Resurrection Remix OS Beta 3!
Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Cacciu said:
Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Click to expand...
Click to collapse
It's been awhile since I used SuperSU so I might be fuzzy: SuperSU has two components, 1) the .zip portion installed from TWRP and 2) the APK. The zip is like "the framework/service/su" part and the APK is the app that just tracks and loads the DB with which apps or services have been granted SU access.
My question is "Which of these did you uninstall?" : OR: Did you uninstall both? Maybe only uninstalling one or the other causes an 'out of sync' condition.
Anyway: This version of SuperSU https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 discussed in that thread has the APK in the .zip file. By definition all TWRP recoveries are rooted and can do what they want to like installing SuperSU.
What happens after you boot seems more likely to be about left-over crud from the APK / DB component, (and I'm guessing here), so if the SuperSU APK is still there, I'd clear it's data entirely, perhaps get rid of it entirely if you can and reinstall the .zip that contains all parts of SuperSU (maybe they all do now) from that link ^^. Make sure that link I gave is the one you want (systemless, etc).
TWRP should've done the heavy lifting during SuperSU install since it's already rooted. If it didn't, then keep the log from TWRP and look over it's install steps during the SuperSU install. Post it here maybe.
Thanks for the answer.
I uninstalled the apk.
I already tried to install the apk directly and also installing it from the zip, and there was either a message like "no root detected" or " root is corrupted".
I also deleted the su folder, uninstalled the apk and reinstalled the zip. But it was always the same: the apk did either say it's not rooted or did not install/show in the apps.
Probably i have to unroot and root it, or do you have any other idea?
TWRP Terminal
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Cacciu said:
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Click to expand...
Click to collapse
You might be out of luck if you deleted the su directory or any other related to binary su code. I'm not sure why you couldn't do a reinstall of the original SuperSU .zip file. You've got that whole 'catch-22' thing going right now.
The only thing I'm wondering about is whether a certain amount of cleanup has to take place before you can just roll SuperSU*.zip over an old mangled version and get it to work. Do you get errors in TWRP when trying to reinstall the entire package?
---------- Post added at 02:48 PM ---------- Previous post was at 02:05 PM ----------
I downloaded this version of SuperSU (which may or may not be what you used, but you of course want the one you used): http://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip
Then I unzipped it and the installer script for not only the binary parts but the apk is here .\SR1-SuperSU-v2.82-SR1-20170608224931\META-INF\com\google\android\updater-binary. (updater-script is a dummy). It's kind of old school and is very easy to understand (the shell script that installs it).
All the files that it pushes onto the SD are easy to find and use, although you have to keep SELinux settings in mind.
It's worth taking a look at if you want to try to rebuild the wrecked version or if you want to just reapply the zip and have a better understanding of any errors it spits out.
Good luck.