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
So, by going into the settings menu of the FTV and toggling the ADB Debug flag, this allows for installing via a push from ADB.
The text that is displayed when changing this value also says that by enabling the setting, it allows for package installs from unknown sources.
Is this not quite the case though?
Using ES File Manager, when selecting an apk package located in the downloads folder on the device, the message shown in the attached screenshot appears.
Since there's no way to do so from the front-end, I am assuming that we will need root to change the flag to truly allow installing from any source?
Any possible way to do this without root?
mkhopper said:
So, by going into the settings menu of the FTV and toggling the ADB Debug flag, this allows for installing via a push from ADB.
The text that is displayed when changing this value also says that by enabling the setting, it allows for package installs from unknown sources.
Is this not quite the case though?
Using ES File Manager, when selecting an apk package located in the downloads folder on the device, the message shown in the attached screenshot appears.
Since there's no way to do so from the front-end, I am assuming that we will need root to change the flag to truly allow installing from any source?
Any possible way to do this without root?
Click to expand...
Click to collapse
Yeah, this isn't currently possible for the public. There is a root exploit(s) already developed but they have not been released yet. The developer, jcase, said he will release an exploit on the same day the upcoming Fire TV update is pushed (the exploit will not be compatible with the update so if you want it you'll need to follow the instructions in the other thread for blocking OTA updates).
mkhopper said:
Any possible way to do this without root?
Click to expand...
Click to collapse
Are you having issues with ADB? We can probably help you get those resolved.
Chahk said:
Are you having issues with ADB? We can probably help you get those resolved.
Click to expand...
Click to collapse
Thanks, but no. I use the automatic tool to push packages with no problems. I was just looking for other methods of package installation that could be done directly while on the FTV.
mkhopper said:
Thanks, but no. I use the automatic tool to push packages with no problems. I was just looking for other methods of package installation that could be done directly while on the FTV.
Click to expand...
Click to collapse
Not at this time. Amazon disabled side-loading of APKs from the device itself. Root would be the only way to get around that.
mkhopper said:
Thanks, but no. I use the automatic tool to push packages with no problems. I was just looking for other methods of package installation that could be done directly while on the FTV.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2715315
Sent from my MZ617 using XDA Premium 4 mobile app
Kramar111 said:
http://forum.xda-developers.com/showthread.php?t=2715315
Click to expand...
Click to collapse
several days ago it occurred to me to alternatively use sshd for terminal access, because:
-a) I feel a little unsafe leaving adb wifi enabled all the time (ok it's only a small thing to turn it on and off, but still) - and for security reasons there is no way to enable/disable it programmatically e.g. from a script/shell/terminal/app (well theoretically this is not exactly true, but practically it is)
-2) some people (i.e. me) would like to do shell/terminal remotely sometimes, rather than on the AFTV (and other people don't have/want a keyboard)
ssh access makes a great alternative to Term.apk, but the problem is:
- Term.apk and/or (pick your favorite android ssh server) don't have permission to run e.g. "pm install foo.apk" - it will fail. (btw 'pm' is a great command, take a look sometime at all the options. it shares a lot of functions as the adb command itself. 'am' is another fun command...)
- so, the hilarious workaround of enabling adb wifi, "adb connect", and then finally "adb shell" or "adb install" etc., is still required. (b/c the adb user is in the 'shell' group, among others - giving it permission to run /system/bin/pm) - oh well.
for random reference:
Code:
127|[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
[email protected]:/ $ exit
[email protected]:/ $ id
uid=10009(app_9) gid=10009(app_9) groups=1015(sdcard_rw),1028,3003(inet),50009(app_40009)
(also note it appears the adb shell user might possibly have 'mount' abilities, but since the /dev/block/sd* nodes permissions' are really locked up, who knows...)
I want to unlock LTE on my phone.
Anyone know how to enable it?
deltadiesel said:
I want to unlock LTE on my phone.
Anyone know how to enable it?
Click to expand...
Click to collapse
Check out this link: https://forum.xda-developers.com/g4/general/guide-enabling-lte-bands-t3137818
if you haven't already.
sdembiske said:
Check out this link: https://forum.xda-developers.com/g4/general/guide-enabling-lte-bands-t3137818
if you haven't already.
Click to expand...
Click to collapse
It says permission denied
I am rooted.
Whats the problem?
Tried that link can't get passed permission denied
What SuperSU everyone using I'm still on 2.,82 says I'm rooted but maybe features are disabled
deltadiesel said:
It says permission denied
I am rooted.
Whats the problem?
Tried that link can't get passed permission denied
Click to expand...
Click to collapse
If you're referring to the link above that I posted, works fine for me. Maybe security setting in your browser - suggest you try looking at the security settings for the browser you're using or try a different browser.
Other option is to go to Google Search (preferably on a PC) and search XDA-Guide: Enabling LTE Bands.
sdembiske said:
If you're referring to the link above that I posted, works fine for me. Maybe security setting in your browser - suggest you try looking at the security settings for the browser you're using or try a different browser.
Other option is to go to Google Search (preferably on a PC) and search XDA-Guide: Enabling LTE Bands.
Click to expand...
Click to collapse
When I go to SuperSU is says denied
I need SuperSU pro I think
What is latest supersu
Its not my browser
I'm talking about when I run the line to enable it
Permission denied
deltadiesel said:
When I go to SuperSU is says denied
I need SuperSU pro I think
What is latest supersu
Click to expand...
Click to collapse
SuperSU doesn't have anything to do with accessing a link. I'm on v2.82, the latest update I've received to-date.
If using Chrome on your phone, turn off Safe Browsing in Settings > (under Advanced heading) > Privacy.
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
deltadiesel said:
Its not my browser
I'm talking about when I run the line to enable it
Permission denied
Click to expand...
Click to collapse
Try enabling setenforce 0 in Terminal Emulator.
Just type in the following (enter each command separately):
su
setenforce 0 (to set permissive) or setenforce 1 (to re-enable enforcing)
and confirm with: getenforce
Failing that, it may be hard coded in your rom which may put you out of luck.
sdembiske said:
SuperSU doesn't have anything to do with accessing a link. I'm on v2.82, the latest update I've received to-date.
If using Chrome on your phone, turn off Safe Browsing in Settings > (under Advanced heading) > Privacy.
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
Try enabling setenforce 0 in Terminal Emulator.
Just type in the following (enter each command separately):
su
setenforce 0 (to set permissive) or setenforce 1 (to re-enable enforcing)
and confirm with: getenforce
Failing that, it may be hard coded in your rom which may put you out of luck.
Click to expand...
Click to collapse
That works through terminal on my phone
Seems like running commands on my compute r it won't switch to root
Either way DFS isn't working now
Can't select my device
deltadiesel said:
Its not my browser
I'm talking about when I run the line to enable it
Permission denied
Click to expand...
Click to collapse
deltadiesel said:
That works through terminal on my phone
Seems like running commands on my computer it won't switch to root
Either way DFS isn't working now
Can't select my device
Click to expand...
Click to collapse
One other thought: failing to first enter adb shell will give that result on your PC.
The following worked for me -i.e., did not get permission-denied, on my laptop.
adb shell
su
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
sdembiske said:
One other thought: failing to first enter adb shell will give that result.
The following worked for me -i.e., did not get permission-denied.
adb shell
su
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
Click to expand...
Click to collapse
This doesn't work for me off my computer
It only works in terminal manager. It switches to root after su
Anyways now that I'm in where is this BAND tab in DFS
deltadiesel said:
This doesn't work for me off my computer
It only works in terminal manager. It switches to root after su
Anyways now that I'm in where is this BAND tab in DFS
Click to expand...
Click to collapse
With respect to the Band tab in DFS - post your questions now to the link I provided in the 1st instance.
If you do not have LGMobileDriver_WHQL_Ver_4.2.0 installed on your PC you will have problems with adb.
sdembiske said:
With respect to the Band tab in DFS - post your questions now to the link I provided in the 1st instance.
If you do not have LGMobileDriver_WHQL_Ver_4.2.0 installed on your PC you will have problems with adb.
Click to expand...
Click to collapse
That is installed
U know what forget this. Probably won't be able to enable band I want anyway
Wasting time
Made a new thread as seems this is demanded option. Some people already checked this and looks like this works. I can't check right now but if you want, please check and post if it works for you.
Restriction is phone number country code based, can be bypassed. Also looks like its developers left setting to disable country checks at all. To do that, you just need to change android setting 'pixel.oslo.allowed_override' to '1' or 'true'.
Connect Pixel 4 with developer mode and execute command in adb shell:
Code:
adb shell setprop pixel.oslo.allowed_override true
or
Code:
adb shell "setprop persist.pixel.oslo.allowed_override true; setprop ctl.restart zygote"
or edit system/build.prop with some app (eg. MagiskHide Props Config)
You need root to do this.
Also there is Xposed Module in xposed manager to do this automatically called "EnableSoliOnPixel4", here's thread about it https://forum.xda-developers.com/pixel-4-xl/themes/success-enable-soli-china-t3994917
Do I need root permission to execute this command via adb? Thanks
Sent from my Google Pixel 2 using XDA Labs
Monazite said:
Do I need root permission to execute this command via adb? Thanks
Sent from my Google Pixel 2 using XDA Labs
Click to expand...
Click to collapse
Yes, without root you can’t edit system props
Eugnis said:
Yes, without root you can’t edit system props
Click to expand...
Click to collapse
getting failed to set property reply. any idea what i'm doing wrong?
Does it mean that I still can use soli in any country even that country doesn't support for it ?
For example, If I traveled to Japan one day, I still can use soli after enable soli by this xposed module ?
Kris
omar5099 said:
getting failed to set property reply. any idea what i'm doing wrong?
Click to expand...
Click to collapse
Looks like ADB not received root rights on phone. To check this use
Code:
adb shell su
if you receive response ' su: not found ' then you should enable root access for adb on phone (with supersu or similar)
Also you can set this prop with MagiskHide Props Config from phone if you used Magisk to root it
Kris Chen said:
Does it mean that I still can use soli in any country even that country doesn't support for it ?
For example, If I traveled to Japan one day, I still can use soli after enable soli by this xposed module ?
Kris
Click to expand...
Click to collapse
Yes, this setting just disable country check at all. So Soli will work worldwide
Eugnis said:
Looks like ADB not received root rights on phone. To check this use
Code:
adb shell su
if you receive response ' su: not found ' then you should enable root access for adb on phone (with supersu or similar)
Also you can set this prop with MagiskHide Props Config from phone if you used Magisk to root it
Click to expand...
Click to collapse
I've obtained root for ADB shell via this command, however none of those 2 original adb lines are working. I'm still getting the failed to set property reply.
Any help appreciated...
Now I gotta root my phone and lose automatic updates just to be able to use it normally. Thanks a lot, Google!! _l_
You will still get automatic updates, you can root your phone, set the persistent property, and remove the root. Should persist across updates.
Bogega said:
I've obtained root for ADB shell via this command, however none of those 2 original adb lines are working. I'm still getting the failed to set property reply.
Any help appreciated...
Click to expand...
Click to collapse
yes same here, any1 got this to work ? thanks
Pixeling said:
You will still get automatic updates, you can root your phone, set the persistent property, and remove the root. Should persist across updates.
Click to expand...
Click to collapse
So if I set the property and then unroot, it will persist even after OTA updates? No need to root again and set it again after every OTA?
aco.falc said:
So if I set the property and then unroot, it will persist even after OTA updates? No need to root again and set it again after every OTA?
Click to expand...
Click to collapse
That's what I suspect since the property lives in /data which is not changed/erased after OTA. I've not tried it myself however that's probably what I will do when I get the phone.
aco.falc said:
So if I set the property and then unroot, it will persist even after OTA updates? No need to root again and set it again after every OTA?
Click to expand...
Click to collapse
Performing some more reading on the subject, there is a possibility that unlocking the bootloader by itself trips safetynet which in turn prevents OTA. I can't know whether this is true for sure, but in this case keeping Magisk root shall hide that and let you download the OTA.
Before applying the OTA you should use magisk to restore the boot.img, let the OTA install, and then let Magisk install itself to the other inactive flash slot where the OTA is. That will make sure that root is kept intact post update and keep hiding that the bootloader is unlocked. Can anyone confirm?
WORKED
hello, i can confirm its working, steps to follow :
when u flash the magisk_patched image the phone wont boot at first, so u have to flash the boot.img then reflash the magisk_patched.
then the phone will boot normally.
after that, download terminal from play store, and type in it : SU , this will ask u for root permissions
then u need to type these 3 commands within the terminal :
setprop pixel.oslo.allowed_override true
setprop persist.pixel.oslo.allowed_override true
setprop ctl.restart zygote
then motion sense will turn on.
enjoy!
if u need detailed steps about the whole thing let me know
sta3b said:
hello, i can confirm its working, steps to follow :
when u flash the magisk_patched image the phone wont boot at first, so u have to flash the boot.img then reflash the magisk_patched.
then the phone will boot normally.
after that, download terminal from play store, and type in it : SU , this will ask u for root permissions
then u need to type these 3 commands within the terminal :
setprop pixel.oslo.allowed_override true
setprop persist.pixel.oslo.allowed_override true
setprop ctl.restart zygote
then motion sense will turn on.
enjoy!
if u need detailed steps about the whole thing let me know
Click to expand...
Click to collapse
Can confirm that typing these commands in terminal did the trick. Used 'Terminal Emulator for Android' app from playstore.
And I skipped first steps (flashing boot.img etc) as I'm already rooted.
Thanks!
Bogega said:
Can confirm that typing these commands in terminal did the trick. Used 'Terminal Emulator for Android' app from playstore.
And I skipped first steps (flashing boot.img etc) as I'm already rooted.
Thanks!
Click to expand...
Click to collapse
It works for me! Thank you!
Do I need to do this all over again when I reboot my phone?
It seems that when rebooting the phone the soli is disabled again, can someone confirm?
Also I read here something about unrooting? can I really root and unroot everytime I want and retain OTA updates?
chris111111 said:
It works for me! Thank you!
Do I need to do this all over again when I reboot my phone?
Click to expand...
Click to collapse
Soli doesn't survive reboots if you're using this method.
There's a magisk module (non Xposed) which solves this though (https://forum.xda-developers.com/pixel-4-xl/themes/enable-soli-contries-magisk-module-t3997035)
wolfgangam31 said:
It seems that when rebooting the phone the soli is disabled again, can someone confirm?
Also I read here something about unrooting? can I really root and unroot everytime I want and retain OTA updates?
Click to expand...
Click to collapse
correct, rebooting the phone will cause SOLI to get disabled, you need to re-enter the commands in the terminal to get it to work again
Android 9 added a new feature which allows for the temporary rotation of the screen, with the press of a button would appear when the phone is put into landscape orientation. MIUI for some reason has decided to exclude it, we're at Android 11 and it still doesn't have it. I was wondering if Xiaomi.EU ROM has this feature, or would I have to go with a custom ROM?
do you use tasker? could try the auto-rotate for chosen apps profile found in this thread.
i used it fine for both ROG phone II and this Alioth phone. i just set it for maps, youtube vanced etc.
works great. not sure i'd recommend the other profiles, they may well be device specific
reg66 said:
do you use tasker? could try the auto-rotate for chosen apps profile found in this thread.
i used it fine for both ROG phone II and this Alioth phone. i just set it for maps, youtube vanced etc.
works great. not sure i'd recommend the other profiles, they may well be device specific
Click to expand...
Click to collapse
Cool, this could be a workaround for my issue, just enabling rotation in some apps. I'll try it out, thanks!
It might be a late reply, but in terminal emulator as root you can type this command: "settings put secure show_rotation_suggestions 1" without the quotes and it will enable rotation suggestions when you rotate the screen. You can also use this same command in FKM scripts section and set it to run on boot. If you're not rooted then you must use adb shell on a PC with adb debugging enabled in developer options and use this command: " pm shell settings put secure show_rotation_suggestions 1" without the quotes. After a reboot the setting is disabled again so you have to run the command after each reboot.
pawelmiernik said:
It might be a late reply, but in terminal emulator as root you can type this command: "settings put secure show_rotation_suggestions 1" without the quotes and it will enable rotation suggestions when you rotate the screen. You can also use this same command in FKM scripts section and set it to run on boot. If you're not rooted then you must use adb shell on a PC with adb debugging enabled in developer options and use this command: " pm shell settings put secure show_rotation_suggestions 1" without the quotes. After a reboot the setting is disabled again so you have to run the command after each reboot.
Click to expand...
Click to collapse
THANK YOU SO MUCH! This has always been one of the reasons I hated MIUI, now I finally get to enjoy this feature that MIUI has chosen to hide for some reason!
CharlieMHz said:
THANK YOU SO MUCH! This has always been one of the reasons I hated MIUI, now I finally get to enjoy this feature that MIUI has chosen to hide for some reason!
Click to expand...
Click to collapse
Ikr it's such a useful thing to have!
@pawelmiernik I just registered to say that you are a frigging legend, thank you so much!
Absolutely idiotic that they left out this option somewhere in the settings. Especially when you can reactivate the already implemented button with such a workaround. Ridiculous.
pawelmiernik said:
It might be a late reply, but in terminal emulator as root you can type this command: "settings put secure show_rotation_suggestions 1" without the quotes and it will enable rotation suggestions when you rotate the screen. You can also use this same command in FKM scripts section and set it to run on boot. If you're not rooted then you must use adb shell on a PC with adb debugging enabled in developer options and use this command: " pm shell settings put secure show_rotation_suggestions 1" without the quotes. After a reboot the setting is disabled again so you have to run the command after each reboot.
Click to expand...
Click to collapse
Thanks for this, would like to add that another way of having it persist is to use SetEdit and add show_rotation_suggestions 1 to the secure table. You'll need to give the SetEdit app permissions to write to the secure table. You can do it with root but if you're not rooted you can use adb, just be sure to enable "usb debugging (security settings)" as well.
pawelmiernik said:
It might be a late reply, but in terminal emulator as root you can type this command: "settings put secure show_rotation_suggestions 1" without the quotes and it will enable rotation suggestions when you rotate the screen. You can also use this same command in FKM scripts section and set it to run on boot. If you're not rooted then you must use adb shell on a PC with adb debugging enabled in developer options and use this command: " pm shell settings put secure show_rotation_suggestions 1" without the quotes. After a reboot the setting is disabled again so you have to run the command after each reboot.
Click to expand...
Click to collapse
Just to add on to this, for me, the settings stayed even after a restart, so I didn't need to run it again after reboot.
I think it's because they added this to MIUI 13. I recently bought a POCO F3 and it had it built in. Finally. There is hope in this world.
Weslington9 said:
I think it's because they added this to MIUI 13. I recently bought a POCO F3 and it had it built in. Finally. There is hope in this world.
Click to expand...
Click to collapse
How to turn on this feature, I am on miui13 but can't find it ?