Related
[How to] Configure Terminal Emulator to use Correct BusyBox & Improve Shell Features
A little info on Android, Terminal Emulator, and Busybox
I'm very new to Android. I just got my first device a few months ago(my A100). I have used linux and other forms of unix off and on for over a decade though so I do have some applicable knowlege.
After writing Flashex I have noticed allot of people with miss configured environment variables for Terminal Emulator. The defaults in Terminal Emulator are NOT configured to use the right Busybox. This can make doing ALLOT of the stuff around here seem allot more complex then it is.
How to improve the way Terminal Emulator works
==============================================
(Note: I'm going under the assumption that Busybox is located in /system/xbin. It should be normaly, though it doesn't matter for this as long as you know the correct location and can put in place of /system/xbin in these directions)
1) Launch Terminal Emulator.
2) Look in the Menu in the upper right hand corver and select "Preferences".
3) Scroll down to the "Shell" section of "Preferences".
4) Select "Command Line" within the "Shell" section of "Preferences" and change it to the following;
/system/xbin/sh -u
Then Select "OK".
5) Select "Initial Command" within the "Shell" section of "Preferences" and change it to the following;
export PATH=/system/xbin:$PATH
Then Select "OK"
6) Now you will probably want to scroll up and change the color of the terminal background and text in the "Text" section of "Preferences".
Congratulations! You should now have a Bourne Shell(sh) with, color coded file types, TAB auto complete, and the correct Busybox version in the Terminal Emulator! YAY!
Why do I keep getting permission denied in TM?
helikido said:
Why do I keep getting permission denied in TM?
Click to expand...
Click to collapse
Is your device rooted? Do you have busybox installed?
helikido said:
Why do I keep getting permission denied in TM?
Click to expand...
Click to collapse
You may be getting the permission denied error if you used This root method because it used a non standard install of Busybox to do the job.
It can be updated from what I understand by just downloading the J Rummy Busybox installer from play.google.com and reinstalling Busybox. Also as asked above if you don't have busybox installed you wont be able to point TE to it.
Hope that resolves the issue
Re: [How to] Configure Terminal Emulator to use Correct BusyBox & Improve Shell Featu
I keep getting the same error with terminal emulator and script manager:
Unable to confirm location of BusyBox, please make sure you have busybox installed
Looked in /system/xbin if you have it installed in another location, you can just edit the path at the top of the script
3|[email protected]:/sdcard $
nice share
Confused!
Hey Guys!
After following the steps you mentioned and saved it and closed Terminal emulator and when trying to reopen it it does not open and it is a pre-installed app in my custom ROM so i went to root explorer and deleted it and while am trying to reinstall it from Play store play store does not download any app !!!!! it opens normally it navigates normally and i can press install and accept to the pop up message but keeps making like it is installing while nothing installed !!!
Device : Motorola XT925
ROM : Beanstalk 1009
Android : 4.3.1
Bootloader : Unlocked
BusyBox : BusyBox X+
Please Please Help Me
---------- Post added at 03:48 PM ---------- Previous post was at 03:40 PM ----------
atteya.mohamed said:
Hey Guys!
After following the steps you mentioned and saved it and closed Terminal emulator and when trying to reopen it it does not open and it is a pre-installed app in my custom ROM so i went to root explorer and deleted it and while am trying to reinstall it from Play store play store does not download any app !!!!! it opens normally it navigates normally and i can press install and accept to the pop up message but keeps making like it is installing while nothing installed !!!
Device : Motorola XT925
ROM : Beanstalk 1009
Android : 4.3.1
Bootloader : Unlocked
BusyBox : BusyBox X+
Please Please Help Me
Click to expand...
Click to collapse
I Tried the following :
1. Reboot.
2. Reinstall google play Version 4.4.21
But problem still exist am really upset guys please help me :S
simply go the app settings and clear data. The exact thing is happening to me as soon as i change the path under shell. crashes and when i try opening says . terminal running and immediately closes
atteya.mohamed said:
Hey Guys!
After following the steps you mentioned and saved it and closed Terminal emulator and when trying to reopen it it does not open and it is a pre-installed app in my custom ROM so i went to root explorer and deleted it and while am trying to reinstall it from Play store play store does not download any app !!!!! it opens normally it navigates normally and i can press install and accept to the pop up message but keeps making like it is installing while nothing installed !!!
Please Please Help Me
---------- Post added at 03:48 PM ---------- Previous post was at 03:40 PM ----------
I Tried the following :
1. Reboot.
2. Reinstall google play Version 4.4.21
But problem still exist am really upset guys please help me :S
Click to expand...
Click to collapse
atteya.mohamed said:
Device : Motorola XT925
ROM : Beanstalk 1009
Android : 4.3.1
Bootloader : Unlocked
BusyBox : BusyBox X+
Click to expand...
Click to collapse
Sorry only A100 support allowed here.
But really, eyelash your rom if anything like that happens. Just flash the rom+gapps first and should fix it otherwise factory reset.
Sent from my SPH-L710 using XDA Premium 4 mobile app
This thread is particularity aimed at (rooted) variants with locked bootloaders and (unlocked & rooted)V10's running on Marshmallow.
#1 The issue regarding (locked)V10's running on Lollipop has been solved, see post http://forum.xda-developers.com/showpost.php?p=66037561&postcount=12 for details.
#2 The issue regarding (unlocked)V10 running on Marshmallow has been solved, see post http://forum.xda-developers.com/showpost.php?p=67428231&postcount=41 for details
Note: see http://forum.xda-developers.com/showpost.php?p=66063441&postcount=16 for automated script execution instructions (required to permanently run V4A under SElinux enforcing), and also for instructions on how to install V4A.
#1 (un)solved issue(s):
I've successfully installed V4A 2.4.0.1 but I also wanted to modify the system in order for it to properly work on a SElinux enforcing policy.
I've followed these instructions http://forum.xda-developers.com/showpost.php?p=61242973&postcount=18854 :
su
mount -o rw,remount /system
cd /system/su.d
echo '#! /system/bin/sh' > 50viper.sh
echo '/system/xbin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"' >> 50viper.sh
chown root.root 50viper.sh
chmod 755 50viper.sh
cd /
mount -o ro,remount /system
exit
I skipped the "cd /system/su.d" part as there is no such directory. And skipped the recovery method (locked bloader).
I tried these commands in adb shell and terminal emulator but both methods have failed into mounting the system as rw. When I enter the rw system command there is no error message, but when I try the "echo '#!..." command I get an error that I'm dealing with a Read-Only file system. See printscreen.
{
"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"
}
I've tried various other mount commands.
Issue has been solved, see post http://forum.xda-developers.com/showpost.php?p=66037561&postcount=12 for details.
#2 Marshmallow (un)solved issue(s):
-When I attempted to install V4a's driver I got the I/O error.
-SElinuxmodechanger app is not able to get root access, even though my phone is properly rooted.
Starts at:http://forum.xda-developers.com/lg-v10/themes-apps/setting-viper4android-t3340343/page4 #32 [/I]
Issue has been solved, see post http://forum.xda-developers.com/showpost.php?p=67428231&postcount=41
Instructions from the Verizon variant, unknown if it will help you or not.
1. Disable namespace separation in SuperSU (Restart Phone)
2. Install SELinux and change mode to Persuasive.
3. Install JRummy Busybox app and install into xbin.
4. Install Viper4Android and grant SU access and click Yes to install drivers.
---------- Post added at 01:09 PM ---------- Previous post was at 01:06 PM ----------
I installed the V4A found on this xda link -> http://forum.xda-developers.com/attachment.php?attachmentid=3685304&d=1458144652
corporal_hades said:
Instructions from the Verizon variant, unknown if it will help you or not.
1. Disable namespace separation in SuperSU (Restart Phone)
2. Install SELinux and change mode to Persuasive.
3. Install JRummy Busybox app and install into xbin.
4. Install Viper4Android and grant SU access and click Yes to install drivers.
---------- Post added at 01:09 PM ---------- Previous post was at 01:06 PM ----------
I installed the V4A found on this xda link -> http://forum.xda-developers.com/attachment.php?attachmentid=3685304&d=1458144652
Click to expand...
Click to collapse
I know how to make it work by switching SElinux off.
What I don't want is to have reduced security for the sake of V4A, that's why I want to be able to leave it on enforcing.
On my nexus 5 I was able to successfully flash the SElinux policy zip on lollipop, so the instructions should work.
Is is possible?
I desperately crave viper on my newly rooted LG V10 but don't want to compromise standard security provided by enforced SElinux.
I hope to hear of a viable workaround...
thanks to any that can help!
Just use one of those run-script-on-startup apps and create a script with the contents of 50viper.sh
U
WillyPillow said:
Just use one of those run-script-on-startup apps and create a script with the contents of 50viper.sh
Click to expand...
Click to collapse
It won't work because it can't mount the system as RW.
But I'll give it a shot with the Smanager app.
elvin421 said:
Is is possible?
I desperately crave viper on my newly rooted LG V10 but don't want to compromise standard security provided by enforced SElinux.
I hope to hear of a viable workaround...
thanks to any that can help!
Click to expand...
Click to collapse
I'll try another approach with a startup script.
But when you run the viper4android proces while in permissive mode and switch back to enforcing mode, viper4android will still be working properly(music must be playing while doing this) .
Vasishtha said:
U
It won't work because it can't mount the system as RW.
But I'll give it a shot with the Smanager app.
Click to expand...
Click to collapse
You don't need to mount it. Basically what you have to do is to execute
Code:
/system/xbin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };
on boot with an app.
I used to use 3C Toolbox for this purpose but now I don't use V4A anymore.
EDIT: If you skip the "cd" part, you'll be writing into /, which is RO. So your remounting should have succeeded.
BTW, the tutorial you followed was trying to add a script that executes the command above using a method our ROMs don't support anyway.
Hi there. Have one question: V4A installed and it works with playerpro. Tried with poweramp, it shows working, but no difference in listening. Tried already different settings in poweramp. No success. Has someone an idea?
Thx a lot in advance.
Schuertzi
I flashed this on my T mobile variant http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
WillyPillow said:
You don't need to mount it. Basically what you have to do is to execute
Code:
/system/xbin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };
on boot with an app.
I used to use 3C Toolbox for this purpose but now I don't use V4A anymore.
EDIT: If you skip the "cd" part, you'll be writing into /, which is RO. So your remounting should have succeeded.
BTW, the tutorial you followed was trying to add a script that executes the command above using a method our ROMs don't support anyway.
Click to expand...
Click to collapse
It worked
What does that command actually do?
It did trow out an error though, but V4a was still able to proces under enforcing. See the attachment for details.
Gungrave223 said:
I flashed this on my T mobile variant http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
Click to expand...
Click to collapse
It tried flashing it with flashfire (I can't install twrp/cmw on my variant), but it didn't install. Does it sound better then stock V4a?
I worked out the error message and my script now works flawlessly.
I used Smanager to load the script on boot. The script was extracted from this flashable file: http://forum.xda-developers.com/showpost.php?p=61242973&postcount=18854
The script only has one command:
#! /system/bin/sh
supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
See attachment for the script(rename .txt to .sh after you've downloaded it)
Thanks for pointing me in the right direction @WillyPillow.
V4A now runs on SElinux enforcing without a problem.
If you need instructions on how to setup Smanager in order to run the script on boot, let us know(edit: see http://forum.xda-developers.com/showpost.php?p=66063441&postcount=16 for instructions).
schuertzi said:
Hi there. Have one question: V4A installed and it works with playerpro. Tried with poweramp, it shows working, but no difference in listening. Tried already different settings in poweramp. No success. Has someone an idea?
Thx a lot in advance.
Schuertzi
Click to expand...
Click to collapse
Did you remove the deep_buffer lines in /etc/audio_policy.conf ?
Also, @Vasishtha what the command does is basically allow some operations by mediaserver that was blocked previously to do its work.
EDIT: BTW, I'm pretty curious what the error was
Well done!
Would you kindly post a method of how to execute V4A installation from beginning to end?
Much appreciated!
WillyPillow said:
Did you remove the deep_buffer lines in /etc/audio_policy.conf ?
Also, @Vasishtha what the command does is basically allow some operations by mediaserver that was blocked previously to do its work.
EDIT: BTW, I'm pretty curious what the error was
Click to expand...
Click to collapse
Regarding poweramp:
Do you mean these lines? (see attachment)
What does removing them do and does it have any negative consequences?
The error in your command came from the lack of 'sh' before the supolicy term.
elvin421 said:
Well done!
Would you kindly post a method of how to execute V4A installation from beginning to end?
Much appreciated!
Click to expand...
Click to collapse
-For installing V4A read up on this guide: https://docs.google.com/document/d/15e7xv8AADnl0Ckqg8NiuQMTPLSgkIZCS4hU4Q07H7i4/mobilebasic
Ignore the selinux changing steps.
-Once properly installed (and with SElinux enforcing still active) install Smanager (https://play.google.com/store/apps/details?id=os.tools.scriptmanager)
-Download the script file I provided my post: http://forum.xda-developers.com/showpost.php?p=66037561&postcount=12
-open Smanager->browse to the script file(file should be renamed from .txt to .sh)->tap and hold on the file->select "open as..." ->select "script/executable" ->new window appears->enable the 'SU' and 'BOOT' options and select run.
Viper4android's driver status should now be normal(under SElinix enforcing). check it by opening V4a, open the menu and select 'driver status'
Really appreciate you posted this. I'm afraid it likely confirms my fear that all my failed attempts of installing viper through various methods may have corrupted the relevant resources in my system such that your method is not working for me.
Hopefully by tonight I'll have my device wiped & viper running following a clean install as described above. Again, thank you!
elvin421 said:
Really appreciate you posted this. I'm afraid it likely confirms my fear that all my failed attempts of installing viper through various methods may have corrupted the relevant resources in my system such that your method is not working for me.
Hopefully by tonight I'll have my device wiped & viper running following a clean install as described above. Again, thank you!
Click to expand...
Click to collapse
When installing V4A does It tell you that you may have installed the wrong busybox(even if its the official one) or that your device is not properly rooted?
There's an easy way to get around it, just reflash the rooted rom (via the 'Upgrade' option). Once booted, don't update the su binary yet. Reinstall busybox and open V4A and install it. It'll install properly.
Vasishtha said:
Regarding poweramp:
Do you mean these lines? (see attachment)
What does removing them do and does it have any negative consequences?
The error in your command came from the lack of 'sh' before the supolicy term.
Click to expand...
Click to collapse
Well, from what I've known, it's just a bigger audio buffer, and doesn't get along well with V4A. Disabling that without V4A installed somehow makes the Hifi DAC work only for certain files, but is easily resolvable by putting the lines back.
Anyway, you can consider commenting the lines out to see if it works.
Vasishtha said:
When installing V4A does It tell you that you may have installed the wrong busybox(even if its the official one) or that your device is not properly rooted?
There's an easy way to get around it, just reflash the rooted rom (via the 'Upgrade' option). Once booted, don't update the su binary yet. Reinstall busybox and open V4A and install it. It'll install properly.
Click to expand...
Click to collapse
Hey, finally found the time to attempt the redo & everything was going according to plan even down to your message above about reflashing the rooted rom using 'upgrade' as a workaround for the failed busybox message & the driver installed properly. Then I expected that everything was good as driver status indicated that it was normal & fine but when I played audio it was not processing unfortunately. My question as I try to isolate the problem is which busybox you used? The method you pointed to (google drive) suggested 'busybox on rails' which failed for me then I tried steriksons which also failed & then I applied your workaround. I've heard the JRUMMY busybox is the functional one for our device & I'm attempting your reflash workaround to get jrummy busybox & viper driver running. Hopefully this works rendering the question moot but would help if you could let me know which busybox you used. Thanks
**update**
I've attempted 3 different busybox installs & have gotten the v4a driver to install with each (thanks to your workaround) & while driver shows Enabled & Status Normal with Audio Format Supported - Processing remains NO (using each different buysbox) with a variety of audio sources playing.
Any help beyond this point would be hugely appreciated!!
About the only reason I root my phone is to install AdAway. I'd prefer to not modify the system partition to help make OTA's easier to get and to allow Android Pay to work. AdAway has a flashable .zip file that preps the hosts file to use the systemless root structure that comes along with SuperSU. Unfortunately, that script depends on being able to access the /data partition inside of TWRP which isn't going to happen any time soon on the HTC 10. Fortunately, it is easy for us to manually replicate what the flashable .zip is trying to do.
This isn't a detailed how-to, but more of a set of guidelines. Don't blame me if your phone explodes.
Root the phone with the latest SuperSU.
Download the AdAway_systemless_hosts_v2.zip file from the Unofficial AdAway thread.
Extract the files from inside the zip. We are only interested in two files in the support folder.
Connect the phone to your PC and turn on file transfer mode.
Copy "hosts" and "0000adaway.script" that you just extracted to the internal storage of your phone.
Use a program file Root Explorer to move "hosts" into /su/etc and move "0000adaway.script" into /su/su.d (this probably could have been done with ADB push, but I got permission errors when I tried it that way and I'm impatient and lazy).
Chmod 0755 /su/su.d/0000adaway.script (I used a root shell on the phone via ADB)
Install AdAway (I used the link in the Unofficial AdAway thread.)
Reboot the phone.
Run AdAway like normal. By default it should use /system/etc/hosts which is what you want.
If something doesn't work, figure out why and fix it. I'm happy to answer questions to the best of my ability.
AdAway works without problems here, with simple press activate button.
starbase64 said:
AdAway works without problems here, with simple press activate button.
Click to expand...
Click to collapse
Yup
Sent from my HTC 10 using Tapatalk
starbase64 said:
AdAway works without problems here, with simple press activate button.
Click to expand...
Click to collapse
Yes, but it modifies the /system partition unless you do the trick in OP. If I'm correct, you will have problems with OTA updates and Google Pay if you let AdAway directly modify the hosts file on /system.
Now that TWRP can access /data, can we just flash the zip?
goodtimes50 said:
Now that TWRP can access /data, can we just flash the zip?
Click to expand...
Click to collapse
Yes, you can. I downloaded that zip and apk from the Unofficial AdAway thread linked above. Booted into TWRP, flashed the newest betaSuperSU2.74-2-forceencrypt (not related to this, just so I'd be on the latest version), then the AdAway_systemless_hosts_v2.zip, rebooted and installed the apk and let it run. Rebooted. Showing hosts location as /system32/etc/hosts as the OP says is a good thing, and both files mentioned are in their correct places per Root Browser. [emoji106]
Sent from my HTC 10 using XDA-Developers mobile app
Sorry that it doesn't completely match the thread here but I think my question could fit in here anyway.
Do I suggest correctly that with systemless root, systemless AdAway and the stock recovery OTAs should be fully usable? Since there's no other modification to /system then.
bmwbasti said:
Sorry that it doesn't completely match the thread here but I think my question could fit in here anyway.
Do I suggest correctly that with systemless root, systemless AdAway and the stock recovery OTAs should be fully usable? Since there's no other modification to /system then.
Click to expand...
Click to collapse
I believe that is correct. There hasn't been a new OTA for my phone yet so I can't verify. However, when I do the check for new software it tells me no new updates (as opposed to the message about the files system being corrupt). I believe Android Pay should also work. I have it installed and added a new card, but I haven't tested making a purchase yet.
Thanks for the guide.
My device is rooted, but I didn't found su folder in anywhere when I use Root Explorer with root access, does anyone tell me how to get su folder and make AdAway work?
Fix for AdAway.
matif525 said:
Thanks for the guide.
My device is rooted, but I didn't found su folder in anywhere when I use Root Explorer with root access, does anyone tell me how to get su folder and make AdAway work?
Click to expand...
Click to collapse
Your device may use su, & still not have an su folder (at all) that is used for hosts file (ie systemless root). Just do this..
Download... Terminal emulator.
https://play.google.com/store/apps/details?id=jackpal.androidterm
Open terminal
Then enter these commands.. "Quote"
su
mount -orw,remount /system
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
mount -orw,remount /system
Now open AdAway go to preferences and select option to " Target hosts file"
Select /data/data/hosts
Enjoy..
If you still have ads in apps do this!!!
githyanki said:
Open the 3 dot menu in adaway, chose log DNS request. Enable TCP dump.
Open the app with ads, when ad loads, go back to adaway, and open log.
Long press any entries and chose black list.
Profit
Click to expand...
Click to collapse
All credit where credit is due. I just shared what I read else where.
Read here for more details..
https://github.com/AdAway/AdAway/issues/770
&
http://forum.xda-developers.com/showthread.php?t=2190753&page=143#post68988079
There is a known issue in HTC devices involves S-off. If the above doesn't solve this for you message here I'll follow. Or pm me. I work wierd hours be patient.
Rom Maximus 3.0.0 ( Android 7 ).Any instruction don't works,adaway no blocked ads.
regarding su folder to move files to
FreydNot said:
About the only reason I root my phone is to install AdAway. I'd prefer to not modify the system partition to help make OTA's easier to get and to allow Android Pay to work. AdAway has a flashable .zip file that preps the hosts file to use the systemless root structure that comes along with SuperSU. Unfortunately, that script depends on being able to access the /data partition inside of TWRP which isn't going to happen any time soon on the HTC 10. Fortunately, it is easy for us to manually replicate what the flashable .zip is trying to do.
This isn't a detailed how-to, but more of a set of guidelines. Don't blame me if your phone explodes.
Root the phone with the latest SuperSU.
Download the AdAway_systemless_hosts_v2.zip file from the Unofficial AdAway thread.
Extract the files from inside the zip. We are only interested in two files in the support folder.
Connect the phone to your PC and turn on file transfer mode.
Copy "hosts" and "0000adaway.script" that you just extracted to the internal storage of your phone.
Use a program file Root Explorer to move "hosts" into /su/etc and move "0000adaway.script" into /su/su.d (this probably could have been done with ADB push, but I got permission errors when I tried it that way and I'm impatient and lazy).
Chmod 0755 /su/su.d/0000adaway.script (I used a root shell on the phone via ADB)
Install AdAway (I used the link in the Unofficial AdAway thread.)
Reboot the phone.
Run AdAway like normal. By default it should use /system/etc/hosts which is what you want.
If something doesn't work, figure out why and fix it. I'm happy to answer questions to the best of my ability.
Click to expand...
Click to collapse
Hi there, ive got a mate 8, not sure if this adblocker will work on it but i want to try it out anyway. Ive unzipped the file but which folder in su do i move the files to? screenshot of the folders i have in su
did anybody find away to push adblock to system via rooted.. thx @Chainfire
like terminal emulator? or anyway. thx In advance
Sent From Pixel XL/Rooted
Team Blackout
Try AdAway
http://forum.xda-developers.com/showpost.php?p=69466682&postcount=217
freddienuxx said:
did anybody find away to push adblock to system via rooted.. thx @Chainfire
like terminal emulator? or anyway. thx In advance
Sent From Pixel XL/Rooted
Team Blackout
Click to expand...
Click to collapse
Here you go install go to settings and enable systemless mode https://drive.google.com/file/d/0B6bczptEI-1LNHphSUQxRDg1RWM/view?usp=drivesdk
Here are the instructions for install Adblock without Recovery (e.g. TWRP):
1. Download Adaway from here: https://www.androidfilehost.com/?fid=24588232905720420
2. Download a Terminal emulator from Playstore
3. Give him root (just type in the emulator "su" and allow root
4. Copy/write this in the Emulator and press enter:
mkdir /su/etc; cp /system/etc/hosts /su/etc/hosts; echo "#!/su/bin/sush\nmount -o bind /su/etc/hosts /system/etc/hosts" > /su/su.d/50adaway; chmod 0700 /su/su.d/50adaway
5. Restart your Phone
6. Install Adaway
7. Allow Root
8. Press install and follow the instruction
I hope this helps
Way too complicated. For AdAway there is a check box in pref for systemless now. Just install AdAway and check that box. Don't need to do anything in terminal.
thx brother much appreciated
mrRobinson said:
Way too complicated. For AdAway there is a check box in pref for systemless now. Just install AdAway and check that box. Don't need to do anything in terminal.
Click to expand...
Click to collapse
do you have that adblock apk?
thx
not working for me... downloaded adaway from above link and no systemless box to check in pref that I see. Also tried running the command in terminal emulator but I get an 'event not found' error
update: I had to use the official 'Terminal Emulator for Android', which I wasn't wanting to use at first and used a different one because it would not let me copy and paste the above command line into the emulator, I had to physically type that whole thing out. But it said that the su folder exists which was the only confirmation I received in the emulator. Then I rebooted and installed, all good now!
freddienuxx said:
do you have that adblock apk?
thx
Click to expand...
Click to collapse
in_dmand said:
not working for me... downloaded adaway from above link and no systemless box to check in pref that I see. Also tried running the command in terminal emulator but I get an 'event not found' error
update: I had to use the official 'Terminal Emulator for Android', which I wasn't wanting to use at first and used a different one because it would not let me copy and paste the above command line into the emulator, I had to physically type that whole thing out. But it said that the su folder exists which was the only confirmation I received in the emulator. Then I rebooted and installed, all good now!
Click to expand...
Click to collapse
As Mr. Robinson said too complicated... Just got to the official link below. Download 3.2 and install, open app go to setting and select systemless... Done
http://forum.xda-developers.com/showthread.php?t=2190753
Give Adguard a go, best one I've used yet. Doesn't need root either.
Sent from my Pixel XL using Tapatalk
Adclear from seven is free is just like adguard
But all those non root adblock apps use up battery.
Personally I use Firefox with adblock plus addon
I recently upgraded to the latest Android 12 for my OnePlus 9 Pro. It's working fairly well. I (hopefully) fixed all the tedious issues with root access and SafetyNet. Now there's only one problem the new ROM is causing me: the baked in version of YouTube is newer than the version of YouTube that YouTube Vanced would otherwise install.
I can't just use "uninstall updates" because the version baked in to the ROM is STILL newer than the Vanced version.- I also can't easily just kill it from /system/product/app/YouTube because System has that weird write protection thing on it. It also won't let me just disable it and then install Vanced
Is there any way I could get the Vanced app going? Is there a way to remove the baked-in YouTube app and just install Vanced?
Use adb to uninstall Google's YouTube and install the YouTube vanced app.
If you really want to modify system partition, you can remount it in read/write mode:
Something like this: mount -o rw,remount /system
You can also try disabling the package from command line:
pm disable <package name>
I used debloat app from fdroid it's based off the module
I use the debloat module by itself, just install and run "debloat" from a root terminal, then choose the apps you want to remove.
vponomarev said:
If you really want to modify system partition, you can remount it in read/write mode:
Something like this: mount -o rw,remount /system
Click to expand...
Click to collapse
It's been impossible to remount /system read-write since at least OOS11 due to the dynamic partitions. If you're aware of a way to do this on OOS12, I'd be interested to hear specifics, but a simple mount command won't work on a stock device anymore.
Instal Titanium Backup and freeze the app. Had the same issue as you, now no issue after freezing it.
raghu102 said:
Instal Titanium Backup and freeze the app. Had the same issue as you, now no issue after freezing it.
Click to expand...
Click to collapse
I did this as well with TB!
Hi guys,
The easiest way for me was to downgrade to the latest official Youtube .apk version supported by Vanced (in my case 16.29.39; latest version is shown next to the install button in the Vanced manager). Once you know the correct .apk version, just google it with apkmirror for example. Save it on your desktop; connect your phone; open power shell and downgrade via adb:
adb install -r -d XXXXXXX.apk
Than you can use Vanced Manager to install YouTube Vanced.
After that, I used TeMeFi kickass tool to detach YouTube from the Play Store.
Did the same procedure for YT Music. Rock'n Roll!
@OP
Post above looks the best way to me. Detaching YT from play store would allow you to uninstall it and install Vanced version.