Database Users

[Q] Who can tell me how to run command?

I read a thread,it's DT for Cypress.
It says:
- run the following command
Code:insmod /system/lib/modules/ax8mt.ko
But I don't know how to run the command.Who can tell me what should I do?
sorry for my bad English and thanks for answering

Gourcuff said:
I read a thread,it's DT for Cypress.
It says:
- run the following command
Code:insmod /system/lib/modules/ax8mt.ko
But I don't know how to run the command.Who can tell me what should I do?
sorry for my bad English and thanks for answering
Click to expand...
Click to collapse
i think it says u run it using dmesg in shell
EDIT:
use command prompt
go to ur adb folder
type in:
adb shell dmseg
and don't forget to write the "su"
_________________________________________
end line -------> correct me if I'm wrong...

thanks for answering and I have solved the problem.

or if you want to be easy
using adb,, on page 3 u can see it

Please help me... I've got a similar problem.
I just enabled multitouch for my x8.
In order to enable it I use these commands at terminal emulator:
su (enter)
insmod /system/lib/modules/ax8mt.ko (enter)
I don't want to make multitouch running on startup (so I haven't changed my hw_config.sh) because of an annoying bug... the screen shuts down after several seconds as if I weren't touching it at all!
Can I create a *.sh file with these commands (su and insmod...) so that I can run it everytime I need to enable multitouch instead of writing them in the terminal?
I created and executed (with root explorer) a *.sh file with these exact lines but it didn't work. What did I do wrong? Should I write it differently in the *.sh file?

Cant reboot via terminal.

Hey gius Im trying to reboot via terminal but I cant seem to get it to work. Keep getting "Nor premited!" error.
I tried with both commands and am using a rooted G2 with stock rom.
su reboot - same error
su reboot now- same error.
any ideas? I know there are apps to do it but why is it not working via terminal?

Any reason why you can't just hold the button in and press reboot?

$ su -
# shutdown -r now
it shoulda outta do it then
for just turning off:
# shutdown -h now

ohgood said:
$ su -
# shutdown -r now
it shoulda outta do it then
for just turning off:
# shutdown -h now
Click to expand...
Click to collapse
Hmm Tried that right now and it says shutdown: not found.

I'm getting the same error! I only tried terminal when Gscript Lite gave me a "not permited". Don't know if it's related, but terminal always starts with $ rather than #. The weirdest part is that it DID work through ADB.
I'm S-OFF, root verified. Has anyone else seen this? I've been searching the forums for a while now...

Try
$ su
# busybox killall system_server
Sent from my HTC Vision using Tapatalk

I get busybox: not found, but since I initially thought it was a busybox issue, I have already updated busybox. Per Titanium Backup, I have version 1.18.4-Titanium. Could it be the titanium busybox?
PanCubano said:
Try
$ su
# busybox killall system_server
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse

Having a similar problem with rebooting from terminal "not permitted", I am using Virtuous Unity,and my phone is rooted etc,anybody having any joy getting reboot from terminal working?double checked busybox permissions and are RWX so whats going on???????????????????

Ok restored my nandroid backup of CM7 and reboot from terminal works so for the problem is connected to Virtuous Unity.

got it ! command is:
$su
#reboot -f
hay presto!!!!!!!
EDIT BUT when using a gscripts reboot doesnt work???????????
I have to use the command busybox killall system_server in the script????
I dont get it,what is the problem !!!!!!!!!!!!!!!!

xsteven77x said:
Any reason why you can't just hold the button in and press reboot?
Click to expand...
Click to collapse
This.
Sent from Space using Tapatalk Pro

I know I could, just trying to understand the android system,how it works and why the reboot command works on CM 7 but not on Virtuous Unity, the search for a solution continues...........................

bombadier said:
I know I could, just trying to understand the android system,how it works and why the reboot command works on CM 7 but not on Virtuous Unity, the search for a solution continues...........................
Click to expand...
Click to collapse
I had the same problem on rooted stock, and it has since gone away since I put on CM7. The reason is that it is not just reboot that didn't work. Almost no scripts would run either, and those can be quite helpful. I believe it's a symptom of something larger, but I can't quite place my finger on what.

mjasmin said:
I had the same problem on rooted stock, and it has since gone away since I put on CM7. The reason is that it is not just reboot that didn't work. Almost no scripts would run either, and those can be quite helpful. I believe it's a symptom of something larger, but I can't quite place my finger on what.
Click to expand...
Click to collapse
I can get reboot -f which works but I have to use busybox killall_server to get it work from a script,have tried a few things but literature on the subject is pretty sparse,its not so important but would still like to understand the whole process, but I seem to be in the minority trying to solve this.......
Why I have to use reboot -f on Unity where reboot will do on CM is a mystery,have found a file that seems to define functions on Unity(virtuous-functions.sh), have tried adding REBOOT="$BUSYBOX reboot" to this but doesn't help.
reboot -f it is then!

[Q] Help with MultiTouch and hw_config

Hi all i need someone who help....let's start....
I have custom ROM FroyoBread.v023b Final from doixanh.... 2.2.9
I move ax8mt.ko on sdcard... unplugged usb... open root explorer mount R/W.
copy ax8mt.ko and move to system/lib/modules and paste . ok then i open Terminal emulator wrote "su" and "insmod /system/lib/modules/ax8mt.ko"
then i open hw.config with text editor put in cfg "insmod /system/lib/modules/ax8mt.ko" and reboot after reboot didn't work... i don't know what is fu*king problem and i really need this MT ... pls boy's help me .... :/

You forgot to change permissions to
xx
x
x
And in hw_config.sh you just add this line at the beggining.

where i forgot
x
x
xx?
and i don't know what u talking about hw_config xD

You change permissions to
xx (2x)
x (1x)
x (1x)
In system/etc there is a file called hw_config.sh.. long press on it, open with text editor and add this line "insmod system/lib/modules/ax8mt.ko" (without the ") at the beginning.. then save it and reboot.

i do this but nothing change

Do you have synaptics digitizer or cypress digitizer?

hmm i'm newbie so how i can know what i have omfg :S i'm really sickest person this forum

fenixcro said:
hmm i'm newbie so how i can know what i have omfg :S i'm really sickest person this forum
Click to expand...
Click to collapse
Haha don't worry we were all n00bs once
Go here: http://forum.xda-developers.com/showthread.php?t=1004740
You will have to do a bit of reading but just read through the first post and try to install that module let me know how u get on

ok if i don't have cypress i don't have MT? omfg i can't play PES2011 :// xD
P.S. any thread how install cypress or this is impossible?

fenixcro said:
ok if i don't have cypress i don't have MT? omfg i can't play PES2011 :// xD
P.S. any thread how install cypress or this is impossible?
Click to expand...
Click to collapse
no you can still have MT (its actually dual touch but w/e )
go to the link i gave u in my last post, download v007 and follow the installation instructions in the thread... (copy to /system/lib/modules, change permissions, add line "insmod /system/lib/modules/x8gesture.ko" to hw_config.sh and save, reboot and it should be there. (you might want to double check the installation instructions :L )

i'm really noob or what this didn't work omfg -.-'

fenixcro said:
i'm really noob or what this didn't work omfg -.-'
Click to expand...
Click to collapse
I remember it took ages for me to get dual-touch set up and now it seems so simple ok i'll help you so run me through what u did

ok ... i download x8gesture.ko put in /system/lib/modules/ paste...then i open hw_config wrote insmod /system/lib/modules/x8gesture.ko
then i open terminal emulator to see did it work wrote
"su"
"insmod /system/lib/modules/x8gesture.ko"
then he show me error -12 i think and i almost hit phone on wall... :S
edit:i try on Glow Hockey 2 and didn't work with one finger i move 1 and 2 players in same place -.-' :S i hate this

fenixcro said:
ok ... i download x8gesture.ko put in /system/lib/modules/ paste...then i open hw_config wrote insmod /system/lib/modules/x8gesture.ko
then i open terminal emulator to see did it work wrote
"su"
"insmod /system/lib/modules/x8gesture.ko"
then he show me error -12 i think and i almost hit phone on wall... :S
edit:i try on Glow Hockey 2 and didn't work with one finger i move 1 and 2 players in same place -.-' :S i hate this
Click to expand...
Click to collapse
O.K First go to terminal emulator and type: dmesg | grep "cyttsp-i2c"
If you get something like this: <6>[ 4.185259] cyttsp_i2c_probe: Successful registration cyttsp-i2c
Then go to solution no.1, otherwise go to no.2, if your not sure try both.
Solution 1.
Download ax8mt (whatever version you want) and copy it to /system/lib/modules
Then change permissions to....
Add line: insmod /system/lib/modules/ax8mt.ko to hw_config, save and make sure permissions are correct.
Reboot phone
download multitouch visualiser off market and try using two fingers.
if it doesnt work type "dmesg | grep ax8mt" in terminal emulator and it should say it is loaded, if not go to solution 2.
Solution 2.
copy the x8gesture.ko file to /system/lib/modules
Then change permissions
Add line: insmod /system/lib/modules/x8gesture.ko to hw_config.sh
Save and exit, make sure the permissions are correct
Reboot the phone.
Try in multitouch visualiser using two fingers
if it doesnt work type "dmesg | grep x8gesture" in terminal emulator and it should say it is loaded

i'm on the phone dont know where is thank button xd i will try and i make ss of this but one more qstn if i have now pinch2zoom did i must delete some file?

what happened when u typed dmesg | grep "cyttsp-i2c" in terminal emualtor

i type this and nothing after this :/

Type "su" and then press enter
then type dmesg | grep "cyttsp-i2c"

i'm not rtrd xD i type su and dmesg in new line nothing :/ p. s. have fb for help?

damn ok :L have u tried both of my solutions?
try typing just the word dmesg in terminal emulatior

[Q] How to identify your CPU type

I get a message from another forum, you can identify your grade ( type) of your N4 CPU
on Terminal emulator with command
adb sheel dmesg | grep PVS
I do the command, there is no response as other have. any one have tried on this.

Yes weve tried this. Mine for example is faster. Try rebooting and doing it again.. Sometimes it works
Sent from my Nexus 4 using xda app-developers app

feideqing said:
I get a message from another forum, you can identify your grade ( type) of your N4 CPU
on Terminal emulator with command
adb sheel dmesg | grep PVS
I do the command, there is no response as other have. any one have tried on this.
Click to expand...
Click to collapse
Are you rooted? There's a thread dedicate a day in the general section. I think it also has an SU in the beginning of the line. But I'm not sure, I just copied and pasted.
Sent from my Nexus 4 using Tapatalk 2

You have to be rooted using a terminal app type
Code:
su
dmesg | grep PVS
If you want to do it using adb its
Code:
adb shell
dmesg | grep PVS

and dont forget to turn on USB Debugging in developers options. If u dont have access to them then just open about phone and press build number 7-10 times.

Hi,
http://forum.xda-developers.com/showthread.php?t=2052496

Thread closed per reference above.

get the inode of a file

i'm new here so first of all hello to everyone.
heres my problem. hopefully somebody can help me.
how can i get an inode of a file. that meens to read a
particular part in the data partition. of course that
could only be possible with su, thats clear.

You've got to use the command line for every root thing.
You can get the inode as described here: http://www.cyberciti.biz/faq/howto-print-inode-data-structure/
How to use root commands: http://forum.xda-developers.com/showthread.php?t=2226664

nikwen said:
You've got to use the command line for every root thing.
You can get the inode as described here: http://www.cyberciti.biz/faq/howto-print-inode-data-structure/
How to use root commands: http://forum.xda-developers.com/showthread.php?t=2226664
Click to expand...
Click to collapse
thanks for the quick response.

i find out that ls has no option -i on android to show inodes.
does anybody know another way to get them

xiyuo said:
i find out that ls has no option -i on android to show inodes.
does anybody know another way to get them
Click to expand...
Click to collapse
Compile or use a version of busybox which has it and use that one. Add it to your apps assets and copy it to the data directory of your app. Then use that binary for the ls command.
That part is very difficult on Android. On one device you have got the ls command but the output might look completely different on another phone. (Some time ago someone reported that he noticed "ls" being linked to "ls -l" on one phone. On another phone the option "-l" might be missing.
So it is recommended to use busybox for every root command.

..

nikwen said:
Compile or use a version of busybox which has it and use that one. Add it to your apps assets and copy it to the data directory of your app. Then use that binary for the ls command.
So it is recommended to use busybox for every root command.
Click to expand...
Click to collapse
i did that.
but with
./busybox ls -i
i get
cant execute permission denied.
even if i use su. how could that be?
does anybody know how i get the permission?

xiyuo said:
i did that.
but with
./busybox ls -i
i get
cant execute permission denied.
even if i use su. how could that be?
does anybody know how i get the permission?
Click to expand...
Click to collapse
In Linux you have to add the right to execute it first:
Code:
su
chmod 775 <filename>