Hi all,
I am looking for a Terminal emulator working properly for the media pad but
Terminal Emulator for Android - Apps on Google Play
Access Android's built-in Linux command line shell. Unleash your inner geek!
play.google.com
according to the playstore is not compatible with my device (with android 9).
Can someone tell me if there is any other available?
Thanks in advance
S.
Try Termux
[Termux | F-Droid - Free and Open Source Android App Repository](https://f-droid.org/en/packages/com.termux/ )
Google playstore policy is making it difficult for apps targeted for less than Android 10
Thanks for your reply. Done, I try to take advantage of your expertise. Maybe you can give me the right suggestion.
I want to run a program written by me named 4 (for some heavy math computations, no input, just output to a file, the only thing I need is CPU) but when I run Termux on a Huawei MediaPad M5 I get always permission denied. I managed to find the file blindly in /storage/emulated/0/4.
On two phones without being root I copied it in the home dir of the terminal app and made chmod and run it. Very easy
But here even cp is refused because permission denied. Is there any way to do this also here without being root?
Thanks in advance
best to ask any questions on reddit.com r/Termux
great community
Chief_Mike said:
best to ask any questions on reddit.com r/Termux
great community
Click to expand...
Click to collapse
Thanks, I will try
Related
Hello XDA-Forum users,
I ask you a question: How does Android Root works ?
I mean, for example, How does it works in Nexus One ?
This would be an understanding question to know more about how I get root from my Phone (Nexus One, for example) from scratch, from sources.
upupupupupup
Rooting basics:
http://lifehacker.com/5342237/five-great-reasons-to-root-your-android-phone
For details on how to do it on your device, Google or use the forum search. Lots of rooting information that is device dependent out there.
It basically gives your phone permission to do almost anything. It is similar to giving a user in Windows Administrator rights. It is called super user. You can do many things such as removing unwanted apps and overclocking.
This is not what I mean, I asks for an explaining in which the question is "How the root is possible? What active the root ?" Probably a kernel exploit, or stuff like that, to understand the underground passage to take it, from an hack view.
So, How works a root utility (such SuperOneClick) to set gid to 0 ?
Valid question, I am also interested in learning this.
In other words, if I were to perform the rooting manually, where can I find such info?
And some of the question is why su must be in some diredctories, and can't be run from /data/local/tmp for example?
Someone can enlighten us?
diego.stamigni said:
Someone can enlighten us?
Click to expand...
Click to collapse
The general approach is taking advantage of bugs in the android OS
The process works something like this
User crafts some special data that contains a "payload" (the script/executable that we want to run)
User runs a system process that has root privileges and gets it to open the special data
The bug causes the system process to get confused by the data, and ends up running the embedded script
The embedded script runs with the same privileges as the system process, and thus can stuff that normal users aren't allowed to do (e.g. installs the SU app)
Commonly, things such as buffer overflows are used
So after gaining root access, which apps can run as root?
Or the user becomes root(as in desktop), and can run all types of apps?
Can root app(run as root) access everything?? Or app permission still applies?
Is it that system exploit is always used to run root apps?
can someone explain in technical details? not how to root.
are rooting programs open source??
What is the root procedure
Bayint Naung said:
So after gaining root access, which apps can run as root?
Or the user becomes root(as in desktop), and can run all types of apps?
Can root app(run as root) access everything?? Or app permission still applies?
Is it that system exploit is always used to run root apps?
can someone explain in technical details? not how to root.
are rooting programs open source??
Click to expand...
Click to collapse
Hi guys!
I have the same question and after searching and asking find this!
it is good!!
hope it works!
http://stackoverflow.com/questions/...hat-are-the-pre-requisites-for-it-to-work-wha
also look at the suggestedpages at the right of this page!
Im writing a Network Scanner currently in Python/Kivy for Android. I could do everything i wanted if i could execute a Python module called Scapy from the shell(Obviously this is a rooted app), but unfortunately its not possible. Atleast not with alot of work and when the App is finished i dont want my users to have to go through installing countless dependencies to get it working!
I've stumbled along a little unix program called Arp-Scan but i cant find a port for Android. I'm not sure how to port this to Android so i can execute it from a shell.
I have no experience with compiling and needless to say this is frustrating the hell out of me! . This one little stumbling block has been plaguing me for 2 weeks. The rest i will be able to do in pure Python, namely PortScanning and such.
The way the Android OS works is that an APK is unable to use raw sockets. But you are allowed to run a shell as root.
I have the option to use Nmap but if there was ever to be a paid version of my app i would have to buy a license and i simply cant afford it.
All i need is to execute a program from shell: like Arp-Scan to obtain an IP and MAC from the LAN.
Any help will be greatly appreciated.
Thanks in advance.
New to here to share some thoughts: why is it so hard to run an emulator on PC?
Reasons of variety come to my mind, but I mustn't tell so. Just done days long of experiment and all in vain, here's my steps in summary:
1. Installed OpenGAPPS. Failed at starting Play Store. (Unfortunately, Google Play Store has stopped.)
2. Installed an unidentified Dell x86 version of Phonesky. Worked for a few minutes then stopped.
3. Installed Lucky Patcher site's Modded Play Store. Stuck at "Authorization is required. Please log in to your Google Account" message.
4. Init.rc trick: ramdisk.img successfully patched, adb shell always root without a need for adb root command anymore, but SuperSu simply didn't work at all.
5. Started from 27/01 and gave up on 28/02.
This thread is probably a collection of my emotional techie notes. I may reply if anyone asks for a laughter on the methods I used. It's OK. Ain't a developer, but ain't a normal user anymore.
At last, greetings to all! Hope I can learn more in the future from xda forums!
...and not WearOS because this is from an Android 5.1.1 build from 2015
I talked about the Wear framework in this thread, and how it can be partially installed onto the Pace and Stratos
THIS DOES NOT MEAN A FULLY WORKING ANDROID WEAR BUILD!
It doesn't connect to the Wear app, even after installing all the APKs required and following the correct setup procedure (some bluetooth error, even after patching it with the supposed workaround for normal apps, it doesn't work - maybe the Bluetooth stack on these watches doesn't work for Wear)
What it does allow is for standalone wear apps with really simple functions to work. Good examples of this are Wear Bottle Spinner (eliseo.wearbottlespinner.wear) and Interval timer for Android Wear (wearablesoftware.wearintervaltimer), which on this list are "not working" due to lack of wear framework, but work after these files have been copied.
Please do not attempt this if you want a fully stable device, or don't feel comfortable debugging. It may not work for you, and you may end up having to post crash logs or have a not-working device. This is a development thread, it's not fully ready for use yet
Installation
- Download this zip
- Extract it and run the following commands from the folder
Code:
adb root
adb remount
adb push com.google.android.wearable.jar /system/framework
adb push clockwork-system.jar /system/framework
adb push com.google.android.wearable.xml /system/etc/permissions
adb push clockwork-system.xml /system/etc/permissions
adb push ClockworkAmbient.apk /system/priv-app/ClockworkAmbient/ClockworkAmbient.apk
adb reboot
I think this is all that's needed for it to work. My test device has more Wear framework APKs on it than are needed, so I'm not totally sure. If it crashes after doing this, please post a logcat and I'll see if anything else is needed - that's why this is a DEV thread!
These files were taken from the last Android 5.1.1 Wear build for the Gear 2 (itself a port): https://forum.xda-developers.com/gear-2/development/please-help-kernel-compiling-android-t2992953
From having followed the AW porting thread for the Samsung Gear S back in the days I can say the following things:
The Bluetooth stack is indeed different between normal Android and Android Wear but IIRC it should be at least theoretically possible to make it work unless Xiaomi/Huami modified it.
To connect to the AW app it will also require to have all the AW GAPPS properly setup AND the fingerprint of a watch it will recognize with said AW version, even an AW port just won't connect with the app unless there is a proper fingerprint setup in build.prop
On another note great job on doing this and I will be testing it out later today when I will have some free time and an easy way of getting said AW apps.
Hello Quinny, I think you're doing a great job, and it's appreciated. What is the scope of this? I am clear that we will not see Android Wear on our devices, but can Google services and applications be installed? Or would it only be used to install certain applications?
Thanks for your contributions.
zodrac said:
Hello Quinny, I think you're doing a great job, and it's appreciated. What is the scope of this? I am clear that we will not see Android Wear on our devices, but can Google services and applications be installed? Or would it only be used to install certain applications?
Thanks for your contributions.
Click to expand...
Click to collapse
It's to make apps that rely on the Wear framework classes work, but only those that are standalone
Ranomez said:
From having followed the AW porting thread for the Samsung Gear S back in the days I can say the following things:
The Bluetooth stack is indeed different between normal Android and Android Wear but IIRC it should be at least theoretically possible to make it work unless Xiaomi/Huami modified it.
To connect to the AW app it will also require to have all the AW GAPPS properly setup AND the fingerprint of a watch it will recognize with said AW version, even an AW port just won't connect with the app unless there is a proper fingerprint setup in build.prop
On another note great job on doing this and I will be testing it out later today when I will have some free time and an easy way of getting said AW apps.
Click to expand...
Click to collapse
@Quinny899 what do you think, would it be possible?
Hi, will this work with this?
https://play.google.com/store/apps/details?id=prox.lab.calclock&hl=cs
urbami said:
Hi, will this work with this?
https://play.google.com/store/apps/details?id=prox.lab.calclock&hl=cs
Click to expand...
Click to collapse
No
Hello there! I think you are doing a fanstastic job! But I have a problem, I can't do adb remount... It says permission denied. Any help is appreciated
Qufy said:
Hello there! I think you are doing a fanstastic job! But I have a problem, I can't do adb remount... It says permission denied. Any help is appreciated
Click to expand...
Click to collapse
You need to be running a rooted boot image and have successfully run "adb root" before remount.
Quinny899 said:
You need to be running a rooted boot image and have successfully run "adb root" before remount.
Click to expand...
Click to collapse
adb root runs successfully. As for the rooted boot image... Does it mean I need a custom recovery image? (Like TWRP?)
Qufy said:
adb root runs successfully. As for the rooted boot image... Does it mean I need a custom recovery image? (Like TWRP?)
Click to expand...
Click to collapse
What does adb root return? Can you send a screenshot?
Quinny899 said:
What does adb root return? Can you send a screenshot?
Click to expand...
Click to collapse
It returns nothing so I am not sure :/
https://imgur.com/TUeo3ky
Qufy said:
adb root runs successfully. As for the rooted boot image... Does it mean I need a custom recovery image? (Like TWRP?)
Click to expand...
Click to collapse
You have to boot (not flash) an boot image with root support and run the commands directly then.
Do a search for root Amazfit, there are some guides.
GreatApo said:
You have to boot (not flash) an boot image with root support and run the commands directly then.
Do a search for root Amazfit, there are some guides.
Click to expand...
Click to collapse
I will try that thanks
Qufy said:
It returns nothing so I am not sure :/
https://imgur.com/TUeo3ky
Click to expand...
Click to collapse
Nothing = it didn't work.
If it works it says "adbd restarting as root"
Quinny899 said:
Nothing = it didn't work.
If it works it says "adbd restarting as root"
Click to expand...
Click to collapse
Oh ok thanks
Quinny899 said:
...and not WearOS because this is from an Android 5.1.1 build from 2015
I talked about the Wear framework in this thread, and how it can be partially installed onto the Pace and Stratos
THIS DOES NOT MEAN A FULLY WORKING ANDROID WEAR BUILD!
It doesn't connect to the Wear app, even after installing all the APKs required and following the correct setup procedure (some bluetooth error, even after patching it with the supposed workaround for normal apps, it doesn't work - maybe the Bluetooth stack on these watches doesn't work for Wear)
What it does allow is for standalone wear apps with really simple functions to work. Good examples of this are Wear Bottle Spinner (eliseo.wearbottlespinner.wear) and Interval timer for Android Wear (wearablesoftware.wearintervaltimer), which on this list are "not working" due to lack of wear framework, but work after these files have been copied.
Please do not attempt this if you want a fully stable device, or don't feel comfortable debugging. It may not work for you, and you may end up having to post crash logs or have a not-working device. This is a development thread, it's not fully ready for use yet
Installation
- Download this zip
- Extract it and run the following commands from the folder
Code:
adb root
adb remount
adb push com.google.android.wearable.jar /system/framework
adb push clockwork-system.jar /system/framework
adb push com.google.android.wearable.xml /system/etc/permissions
adb push clockwork-system.xml /system/etc/permissions
adb push ClockworkAmbient.apk /system/priv-app/ClockworkAmbient/ClockworkAmbient.apk
adb reboot
I think this is all that's needed for it to work. My test device has more Wear framework APKs on it than are needed, so I'm not totally sure. If it crashes after doing this, please post a logcat and I'll see if anything else is needed - that's why this is a DEV thread!
These files were taken from the last Android 5.1.1 Wear build for the Gear 2 (itself a port): https://forum.xda-developers.com/gear-2/development/please-help-kernel-compiling-android-t2992953
Click to expand...
Click to collapse
Can it delete my ROM(PACEfied)?
Hi is it possible to run google fit directly from watch?
With framewotk or any custom build google fit apk? Anyone test it?
Will the application like a "com.huami.watch.deskclock" and another stock application still works ?
A M A Z F I T S T R A T O S
lensSGzaza said:
Will the application like a "com.huami.watch.deskclock" and another stock application still works ?
A M A Z F I T S T R A T O S
Click to expand...
Click to collapse
Yes.
Hei there!
I just encountered some suspicious behavior on my phone, and I suspect some kind of malware / rootkit.
Background Information
After I accidentally deleted some pictures, I've installed EaseUS MobiSaver to try to recover those.
The scan for deleted files found some of my lost pictures, but also quite some more!
Turns out there are dozens of pictures, respectively screenshots of very random screens like, setting up my clock, browser pages, browsing files, watching YT or VLC, opened apps and so on.
I've attached some of those below.
At first I thought those images are just some kind of framebuffer leftovers or something like that. But then I found that "rootSU.png" image which is baffeling.
Kaspersky, Sophos and Malewarebytes do not find any hints of a infection.
As for my phone / environment
Pocophone F1
PixelExperience 10.0
NoGravityKernel 1.4
Magisk 20.4
So for now my phone is offline, and I would like to investigate what's going on there.
Is there any way to scan the system from external over adb or something?
.
The mentioned rootSU.png picture obviously is a screenshot, made by whomsoever. Yes, an innocent-looking image - sent either via the internet or text - could open your Android phone up to hacking.
Can it be you've run XIAOMI ROOT tool?
BTW, with regards to ADB: If your device is rooted, then install Termux: Termux is a free and open code app that simulates the command shell used in Linux. By doing so, you can introduce all the usual commands and work comfortably from your Android device - you don't need ADB.
jwoegerbauer said:
The mentioned rootSU.png picture obviously is a screenshot, made by whomsoever. Yes, an innocent-looking image - sent either via the internet or text - could open your Android phone up to hacking.
Can it be you've run XIAOMI ROOT tool?
BTW, with regards to ADB: If your device is rooted, then install Termux: Termux is a free and open code app that simulates the command shell used in Linux. By doing so, you can introduce all the usual commands and work comfortably from your Android device - you don't need ADB.
Click to expand...
Click to collapse
Thank you for answer.
No, did not use any XIAOMI Root-tool. Rooting was done via Magisk.
But termux could give me some insight. :good:
Well, despite those suspicious files, I was not able to identify any odd behaving processes.
I guess it's time to wipe and reinstall.