Hi,
This is my first thread on XDA so forgive me if this question has already been answered somewhere else.
I've been using Android Terminal Emulator for a while now my TF101 (with ICS).The device is rooted with busybox 1.20.2-cm9 installed.
Everytime I try to enquire on disk space using the "du" command I get a segmentation fault/ Stopped Signal error. I've attached a picture to show what I mean
I've also got linuxonadroid installed running ubuntu 12.04. When I use the same command line in that environment, no such errors appears.
Please advise .
Thanks
Related
Connect my G1 with my laptop(Ubuntu 8.10 x64)
When I run the adb devices, it only said: List of devices attached
No devices line; It lists one line when I start the emulator program.
And not like the SDK for windows, there is not some folder related to drivers.
Does it support for linux x64? plz help.~
have you activated the debugger in your g1 ?
oh I remember when I was in ubuntu now
you gotta launch adb daemon as root
try this :
adb kill-server && sudo adb devices
and let me know if it worked
dixxa said:
have you activated the debugger in your g1 ?
Click to expand...
Click to collapse
Absolutely, it works fine in Vista x64 with SDK 1.1 r1
I had to do two things to get this to work (although this was on x86) -
1) Build the kernel with the Android drivers enabled. This might not be necessary; I have no idea if they are turned on in the kernels you get from the Ubuntu repository as mine has been custom built for a while, but I'm guessing that they aren't enabled by default because they are in the "staging" area as of 2.6.29.1. So these were in Device Drivers/Staging Drivers/Android.
2) Add a "50-android.rules" file to /etc/udev/rules.d that has this line:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",SYMLINK+="android_adb",MODE="0666"
The idVendor is different if you have an ADP phone, I believe; this was the value worked for mine (non-dev). You can do an 'lsusb' after it's been plugged in and see what shows up. Also, try grepping /var/log/messages for "udev" after you plug it into a USB port and see if there are meaningful messages.
- Chris
Hi all,
I got similar issue here, the main difference is that i got ubuntu 9.04.
running adb daemons as root permit to see devices when it's started normally, but not when in fastboot mode.
I tried all suggestions above (and others!) without success :/
Thanks for any help
noz.geek said:
Hi all,
I got similar issue here, the main difference is that i got ubuntu 9.04.
running adb daemons as root permit to see devices when it's started normally, but not when in fastboot mode.
I tried all suggestions above (and others!) without success :/
Thanks for any help
Click to expand...
Click to collapse
copy the 50-android.rules file you created into a file called 51-android.rules. The problem is related to the order in which things are launched and copying this file to the new name will solve your problem.
I should also note that you will have to restart udev Or reboot or logout/in
to restart udev, In terminal type:
Code:
sudo /etc/init.d/udev restart
sudo is necessary~ thx
Hi all,
After creating 50-android.rules file in /etc/udev/rules.d, I can mount my sdcard on my gPhone to Ubuntu8.04 but I still see no thing when i type command : adb devices. I also did some commands which you gave here. Can anybody help me?
Thanks so much,
NPAK
npak243 said:
Hi all,
After creating 50-android.rules file in /etc/udev/rules.d, I can mount my sdcard on my gPhone to Ubuntu8.04 but I still see no thing when i type command : adb devices. I also did some commands which you gave here. Can anybody help me?
Thanks so much,
NPAK
Click to expand...
Click to collapse
Code:
$ sudo mv /etc/udev/rules.d/50-android.rules /etc/udev/rules.d/51-android.rules/code]
that should fix it ;)
Thanks,
It can work now!
I have the same problem here. adb used to be able to see my phone when I was using Ubuntu 8.10. After I upgraded to 9.04, it never worked. I tried change the udev rule file from 50-** to 51-** or as haykuro suggested to 51-**/code. I also changed the permission to 777. And I did kill and restart adb-server several times under root, but I still get nothing~~~
Can anyone help?
hi, i have a HTC Desire. With 5120MB internal memmory.
Moved all apps with are able to, to sd card.
But iam still less on space.
I found some other threads where is written about using "du" command.
Ok i tried use ConnectBot app and "su".
thant it tels me "command not found" Is there a app with provides linux basic command?
And when i try "df -h" it tels me command " -h" not found.
How do you use the console. why can i not type space for command parameters?
I suppose there is somewhere a big log file or something else. but how can i figure it out? Normaly would i use with linux "du -h --max-depth=1" but with out this command?
You can't use su because your phone is not rooted. Google Unrevoked, download it, follow the instructions, and voila! You have root! "Bow before me, for I am root."
Also, the command you are looking for MAY be part of busybox. To get busybox, I suggest flashing a ROM with busybox such as LeeDrOiD, or AuraxTSense.
Swyped from my HTC Desire running LeeDrOiD 2.3d with Tapatalk.
Hi, my phone is already rooted.
And thanks for the tip with bussybox.
I rebootet my phone to recovery mode, attached it to usb, and used the adb command from sdk on my pc to conenct.
Full tutorial: http://android.modaco.com/content/htc-desire-desire-modaco-com/307587/busybox-on-rooted-desire/
Then i could with:
du -h -d 1 /
check where my space is gone to.
GreenRover said:
Hi, my phone is already rooted.
And thanks for the tip with bussybox.
I rebootet my phone to recovery mode, attached it to usb, and used the adb command from sdk on my pc to conenct.
Full tutorial: http://android.modaco.com/content/htc-desire-desire-modaco-com/307587/busybox-on-rooted-desire/
Then i could with:
du -h -d 1 /
check where my space is gone to.
Click to expand...
Click to collapse
Instead, You could try DiskUsage ( http://www.appbrain.com/app/diskusage/com.google.android.diskusage )
I apologize for asking this because I'm SURE it's been asked - just finally gave up on my search. I performed "FIRST" and "SECOND" steps but stopped when I read this: "If you just want a stock, rooted phone with no custom recovery, no plans to flash custom roms, etc. then you can stop HERE." ... This is where I want to be (I think) yet when i downloaded "Shell Terminal Emulator" and then ran the "su" command - it would never take me to a hash prompt - so it seems (to me) like i REALLY do not have root. Do I need to do more?
ATT JB 4.1.1 Galaxy SIII
Get an app from the play store that checks if you have root or not and use it.
Sent from my SGH-T999 using xda app-developers app
ANSWERED
Thanks Pennycake - I already had two apps indicating that I infact DO have root access - but having a little Solaris background - I wanted to see it on the Command Line.
One word of advise - NEVER get an app from the Playstore called: Shell Terminal Emulator (version 1.0.1) ... BUT instead get: "Android Terminal Emulator" by Palevich - this performed as expected (su changes the prompt to: #).
Thanks Again!
Hi everyone, I'm trying to get a full blown GNU distro of Linux running on my note pro but I've hit a snag. It seems like the device should support it, but every time I try to run a script that creates loopback devices, mounts directories, etc. I get permission errors even though I definitely have root.
Here's where it gets weird. Completel Linux installer fails when it tries to run this command:
Code:
mknod /dev/block/loop255 b 7 255
and it gives this error:
Code:
mknod: /dev/block/loop255: Operation not permitted
Despite what the error says, the script is being run as root. The app automatically opens the terminal and runs the command as root, but I also tried manually executing su and running the same script but the same error occurs.
As an experiment, I tried manually running just that one mknod commad and it works fine. In fact, if I manually execute every line in the bootscript.sh file it all seems to execute perfectly fine. But if I put the exact same mknod command into a .sh file and execute it like this:
Code:
> sh test.sh
Then it gives the same error. Interestingly, if I directly run mknod as a non-root user it does not give me the "Operation not permitted" error, instead it says "Permission denied". I tried some other apps like Debian Kit as well and they seem to give the same error.
Any ideas why it would matter whether I manually enter a command into the terminal or whether I execute the same command indirectly from a file? I tried other terminal apps as well and it made no difference.
Thanks.
Graeme H said:
Hi everyone, I'm trying to get a full blown GNU distro of Linux running on my note pro but I've hit a snag. It seems like the device should support it, but every time I try to run a script that creates loopback devices, mounts directories, etc. I get permission errors even though I definitely have root.
Here's where it gets weird. Completel Linux installer fails when it tries to run this command:
Code:
mknod /dev/block/loop255 b 7 255
and it gives this error:
Code:
mknod: /dev/block/loop255: Operation not permitted
Despite what the error says, the script is being run as root. The app automatically opens the terminal and runs the command as root, but I also tried manually executing su and running the same script but the same error occurs.
As an experiment, I tried manually running just that one mknod commad and it works fine. In fact, if I manually execute every line in the bootscript.sh file it all seems to execute perfectly fine. But if I put the exact same mknod command into a .sh file and execute it like this:
Code:
> sh test.sh
Then it gives the same error. Interestingly, if I directly run mknod as a non-root user it does not give me the "Operation not permitted" error, instead it says "Permission denied". I tried some other apps like Debian Kit as well and they seem to give the same error.
Any ideas why it would matter whether I manually enter a command into the terminal or whether I execute the same command indirectly from a file? I tried other terminal apps as well and it made no difference.
Thanks.
Click to expand...
Click to collapse
try source the script ,eg: . test.sh, this works but i don't know why.
Good idea pheyx! That's a great workaround which basically solves my problem for now... or at least sends me on to the next problem
Thanks for you help.
Graeme H said:
Good idea pheyx! That's a great workaround which basically solves my problem for now... or at least sends me on to the next problem
Thanks for you help.
Click to expand...
Click to collapse
I think I've found the reason. It's due to selinux. The selinux is set to enforced on android from 4.4. I flashed a kernel that sets selinux to permissive and it resolved the issue. Now the complete linux installer ran perfectly without modifying the scripts.
pheyx said:
I think I've found the reason. It's due to selinux. The selinux is set to enforced on android from 4.4. I flashed a kernel that sets selinux to permissive and it resolved the issue. Now the complete linux installer ran perfectly without modifying the scripts.
Click to expand...
Click to collapse
how well is Linux running on it for you?
Sent from my SM-P900 using XDA Premium HD app
Yeah, how well is it running?
I guess it's out of the question both due to speed (Complete Linux Installer uses laggy VNC remote desktop) and hardware (I guess the stylus won't work pressure-sensitive-ish due to VNC), but I'd love to run MyPaint on NotePRO.
Duly.noted said:
how well is Linux running on it for you?
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
Redsandro said:
Yeah, how well is it running?
I guess it's out of the question both due to speed (Complete Linux Installer uses laggy VNC remote desktop) and hardware (I guess the stylus won't work pressure-sensitive-ish due to VNC), but I'd love to run MyPaint on NotePRO.
Click to expand...
Click to collapse
X Window performance is bad if using VNC, is better when using xsdl x server. Also can use fbdev(or fbturbo) native x server(and the cons is in either case must shutdown android stack),but I have no success using these two linux native x server
I´m runnig a Moto G5+ (potter) 7.0 stock rom, rooted with magisk 16.
Since a few days I recognize an error when opening a terminal emulator or using adb from a windows PC and just typing the command
Code:
getprop
from terminal emulator or
Code:
adb shell getprop
from PC the output is
Code:
stack corruption detected
.
I´m not new to android and know how to flash roms or kernels and stuff like this but I´m not so good in terminal commands. I googled for it but the answers I found were a bit above my level of knowledge. Can someone help me out a bit and explain what this message means exactly and how to debug and solve it?
I was able to run this command a few weeks ago without problems, also rooted with magisk. Could it be any third party app or a setting?
Any help much appreciated.
edit: attached a log when typing getprop into the terminal emulator.
get same error