Samsung Galaxy S I9000

Forums › Android › Samsung Galaxy S I9000

1 | ... | 300 | 301 | 302 | 303 | 304 | 305 | 306 | 307 | 308 | 309 | 310 | ... | 427

162 posts

Master Geek

#440403 16-Feb-2011 19:10

Neets:
So, let me see if I have this right, this is what the line should be:
adb shell
dmesg | grep Firmware > /mnt/sdcard/dmesg.txt

After typing adb shell I get:
$
Which is what you'd get in Terminal Emulator after typing (in lower case) su
If the answer is yes, I get diddly squat.

Alright if you're using terminal emulator just type:

su
dmesg | grep Firmware > /mnt/sdcard/dmesg.txt
However just: dmesg | grep Firmware should work.

The first will output the results to a text file on the sdcard, the second should display the results on the screen.

If you've extracted the android SDK, go to control panel, system, advanced, there should be a button 'Enviroment Variables', find path under system variables and hit edit. Add to the end of it ;C:\path\to\adb.exe (mine is ;C:\android\platform-tools). After all that you can open a command prompt and run these commands, it's a long process I know.

adb shell
dmesg | grep Firmware

You still need to turn wifi off than on in both cases.

Neets

1376 posts

Uber Geek

Trusted

#440415 16-Feb-2011 19:31

wazz:
Neets:
So, let me see if I have this right, this is what the line should be:
adb shell
dmesg | grep Firmware > /mnt/sdcard/dmesg.txt

After typing adb shell I get:
$
Which is what you'd get in Terminal Emulator after typing (in lower case) su
If the answer is yes, I get diddly squat.

Alright if you're using terminal emulator just type:

su
dmesg | grep Firmware > /mnt/sdcard/dmesg.txt
However just: dmesg | grep Firmware should work.

The first will output the results to a text file on the sdcard, the second should display the results on the screen.

If you've extracted the android SDK, go to control panel, system, advanced, there should be a button 'Enviroment Variables', find path under system variables and hit edit. Add to the end of it ;C:\path\to\adb.exe (mine is ;C:\android\platform-tools). After all that you can open a command prompt and run these commands, it's a long process I know.

adb shell
dmesg | grep Firmware

You still need to turn wifi off than on in both cases.

Ok, so I already had:
C:\Program Files\Common Files\[insert a bunch of other stuff];C:\android-sdk-windows\tools

And my screen shot, becuase a picture speaks a thousand words. And you may instantly see where I've stuffed up.

Of course the phone is connected via USB cable and I've turned off Wifi and tuned it back on again, while connected.
adb shell

I'm sorry if I'm wasting your time. I just like to get to the bottom of this. I'm like a dog with a bone now. I need to know how to do it :) Then I probably will never use SDK again - haha.

Samsung Galaxy S5 SM-G900I

wazz

162 posts

Master Geek

#440417 16-Feb-2011 19:40

Neets:
Ok, so I already had:
C:\Program Files\Common Files\[insert a bunch of other stuff];C:\android-sdk-windows\tools

And my screen shot, becuase a picture speaks a thousand words. And you may instantly see where I've stuffed up.

Of course the phone is connected via USB cable and I've turned off Wifi and tuned it back on again, while connected.

I'm sorry if I'm wasting your time. I just like to get to the bottom of this. I'm like a dog with a bone now. I need to know how to do it :) Then I probably will never use SDK again - haha.

EDIT: Looks like you dont have root access actually, try adb shell again and check your phone for a su request.

Neets

1376 posts

Uber Geek

Trusted

#440419 16-Feb-2011 19:45

wazz:
Neets:
Ok, so I already had:
C:\Program Files\Common Files\[insert a bunch of other stuff];C:\android-sdk-windows\tools

And my screen shot, becuase a picture speaks a thousand words. And you may instantly see where I've stuffed up.

Of course the phone is connected via USB cable and I've turned off Wifi and tuned it back on again, while connected.

I'm sorry if I'm wasting your time. I just like to get to the bottom of this. I'm like a dog with a bone now. I need to know how to do it :) Then I probably will never use SDK again - haha.

EDIT: Looks like you dont have root access actually, try adb shell again and check your phone for a su request.

nadda, there's no request on the phone for Super User.

Samsung Galaxy S5 SM-G900I

wazz

162 posts

Master Geek

#440420 16-Feb-2011 19:47

Neets:

nadda, there's no request on the phone for Super User.

Try typing su after adb shell and see if it pops up. You'll know when you have root as the $ will change to #.

Neets

1376 posts

Uber Geek

Trusted

#440421 16-Feb-2011 19:48

wazz:
Neets:

nadda, there's no request on the phone for Super User.

Try typing su after adb shell and see if it pops up.

It returns:
adb: not found

And that's what I get in Terminal Emulator, I just tried. And I do get the Super User in Terminal Emulator

EDIT: Does it matter if debugging is connected? I would think it should be connected, that's one of the beauties of SDK is being able to kick start your phone if it's got debugging on.

Samsung Galaxy S5 SM-G900I

defragger

268 posts

Ultimate Geek

#440422 16-Feb-2011 19:51

Neets:
wazz:
Neets:

nadda, there's no request on the phone for Super User.

Try typing su after adb shell and see if it pops up.

It returns:
adb: not found

And that's what I get in Terminal Emulator, I just tried. And I do get the Super User in Terminal Emulator

EDIT: Does it matter if debugging is connected? I would think it should be connected, that's one of the beauties of SDK is being able to kick start your phone if it's got debugging on.

Do it like this

adb shell [enter]
su [enter and accept request on phone]

If you have an '#', then you have superuser access.

EDIT: Yeah make sure your phone is in development mode.

Type "adb devices" initially to make sure your device is connected, then proceed to the shell command.

Wise

Send money globally for less with Wise - one free transfer up to NZ$900 (affiliate link).

wazz

162 posts

Master Geek

#440423 16-Feb-2011 19:52

Neets:
It returns:
adb: not found

And that's what I get in Terminal Emulator, I just tried. And I do get the Super User in Terminal Emulator

EDIT: Does it matter if debugging is connected? I would think it should be connected, that's one of the beauties of SDK is being able to kick start your phone if it's got debugging on.

Yeah you gotta hit enter after adb shell and then type su. You'll just get a device not found error if debugging isnt enabled.

Neets

1376 posts

Uber Geek

Trusted

#440429 16-Feb-2011 19:59

defragger:
Neets:
wazz:
Neets:

nadda, there's no request on the phone for Super User.

Try typing su after adb shell and see if it pops up.

It returns:
adb: not found

And that's what I get in Terminal Emulator, I just tried. And I do get the Super User in Terminal Emulator

EDIT: Does it matter if debugging is connected? I would think it should be connected, that's one of the beauties of SDK is being able to kick start your phone if it's got debugging on.

Do it like this

adb shell [enter]
su [enter and accept request on phone]

If you have an '#', then you have superuser access.

EDIT: Yeah make sure your phone is in development mode.

Type "adb devices" initially to make sure your device is connected, then proceed to the shell command.

Right, I've got Super User access, I have the # and yes, the phone asked me to accept.
I type:
adb devices [enter]
It returns:
adb: not found (I still have the #).

Good Lord, this is turning into something huge when clearly for everyone else it's a piece of p!ss.
Also before trying for adb devices I had tried all variations listed so far of the dmesg.

Samsung Galaxy S5 SM-G900I

wazz

162 posts

Master Geek

#440435 16-Feb-2011 20:03

Neets:

Right, I've got Super User access, I have the # and yes, the phone asked me to accept.
I type:
adb devices [enter]
It returns:
adb: not found (I still have the #).

Good Lord, this is turning into something huge when clearly for everyone else it's a piece of p!ss.
Also before trying for adb devices I had tried all variations listed so far of the dmesg.

Once you've typed adb shell you're pretty much executing commands on the phone. You're in the shell of the phone. So adb commands no longer work, type exit to get back to the normal command prompt. Anyway just type dmesg (once in shell) and see if it brings anything up. You may just have to restart wifi again, anyway here's what it should look like:

http://www.iforce.co.nz/View.aspx?i=tgxdc4oo.jbd.png

Neets

1376 posts

Uber Geek

Trusted

#440437 16-Feb-2011 20:08

wazz:
Neets:

Right, I've got Super User access, I have the # and yes, the phone asked me to accept.
I type:
adb devices [enter]
It returns:
adb: not found (I still have the #).

Good Lord, this is turning into something huge when clearly for everyone else it's a piece of p!ss.
Also before trying for adb devices I had tried all variations listed so far of the dmesg.

Once you've typed adb shell you're pretty much executing commands on the phone. You're in the shell of the phone. So adb commands no longer work, type exit to get back to the normal command prompt. Anyway just type dmesg (once in shell) and see if it brings anything up. You may just have to restart wifi again, anyway here's what it should look like:

http://www.iforce.co.nz/View.aspx?i=tgxdc4oo.jbd.png

The screen shot
Neets the twit

Samsung Galaxy S5 SM-G900I

defragger

268 posts

Ultimate Geek

#440438 16-Feb-2011 20:08

Neets:
defragger:
Neets:
wazz:
Neets:

nadda, there's no request on the phone for Super User.

Try typing su after adb shell and see if it pops up.

It returns:
adb: not found

And that's what I get in Terminal Emulator, I just tried. And I do get the Super User in Terminal Emulator

EDIT: Does it matter if debugging is connected? I would think it should be connected, that's one of the beauties of SDK is being able to kick start your phone if it's got debugging on.

Do it like this

adb shell [enter]
su [enter and accept request on phone]

If you have an '#', then you have superuser access.

EDIT: Yeah make sure your phone is in development mode.

Type "adb devices" initially to make sure your device is connected, then proceed to the shell command.

Right, I've got Super User access, I have the # and yes, the phone asked me to accept.
I type:
adb devices [enter]
It returns:
adb: not found (I still have the #).

Good Lord, this is turning into something huge when clearly for everyone else it's a piece of p!ss.
Also before trying for adb devices I had tried all variations listed so far of the dmesg.

Type "adb devices" when there is no $ or #. Because you are executing the "adb.exe" file here, and giving it a parameter.

So in bold is what you are typing and pressing enter.

C:\Program Files\Android\android-sdk-windows\platform-tools>adb devices
[returns device]

C:\Program Files\Android\android-sdk-windows\platform-tools>adb shell

$su

#[now you can carry on with the dmesg thing]

Neets

1376 posts

Uber Geek

Trusted

#440440 16-Feb-2011 20:14

defragger:

Type "adb devices" when there is no $ or #. Because you are executing the "adb.exe" file here, and giving it a parameter.

So in bold is what you are typing and pressing enter.

C:\Program Files\Android\android-sdk-windows\platform-tools>adb devices
[returns device]

C:\Program Files\Android\android-sdk-windows\platform-tools>adb shell

$su

#[now you can carry on with the dmesg thing]

Yep, doing all that: Not my lucky day

Samsung Galaxy S5 SM-G900I

defragger

268 posts

Ultimate Geek

#440443 16-Feb-2011 20:22

Neets:
defragger:

Type "adb devices" when there is no $ or #. Because you are executing the "adb.exe" file here, and giving it a parameter.

So in bold is what you are typing and pressing enter.

C:\Program Files\Android\android-sdk-windows\platform-tools>adb devices
[returns device]

C:\Program Files\Android\android-sdk-windows\platform-tools>adb shell

$su

#[now you can carry on with the dmesg thing]

Yep, doing all that:

Yeah if it makes you feel better I can't get any further than that either. Hmm...

Neets

1376 posts

Uber Geek

Trusted

#440445 16-Feb-2011 20:25

defragger:
Neets:
defragger:

Type "adb devices" when there is no $ or #. Because you are executing the "adb.exe" file here, and giving it a parameter.

So in bold is what you are typing and pressing enter.

C:\Program Files\Android\android-sdk-windows\platform-tools>adb devices
[returns device]

C:\Program Files\Android\android-sdk-windows\platform-tools>adb shell

$su

#[now you can carry on with the dmesg thing]

Yep, doing all that:

Yeah if it makes you feel better I can't get any further than that either. Hmm...

Ahhh, I'm laughing. Ok, I c@cked up a bit at the beginning becuase I didn't realise about the super user bit. But I've compared screen shots (thanks wazz, that link arrived after I'd hit the quote button). Glad I'm not a complete waste of space. I was starting to think it was a gender thing and I should just back away from the computer.

Samsung Galaxy S5 SM-G900I

1 | ... | 300 | 301 | 302 | 303 | 304 | 305 | 306 | 307 | 308 | 309 | 310 | ... | 427