Optimus S Help!

[djsanchez5]

ok im using screencast and im getting the android screen then it goes to sum wack home screen that i dont recognize. and i dont see android market,sretup,just some default crap that wasnt there from gate. wut do i do now

 

[sfhub]

gRom should be pre-rooted. If that is the case, it should be very simple to get xionia back on.

Could you type in adb shell (or terminal) and post the output:

/system/bin/ls -l /system/bin/su
/system/bin/ls -l /system/app/Super*
/system/bin/ls -l /system/app/super*

 

[djsanchez5]

gRom should be pre-rooted. If that is the case, it should be very simple to get xionia back on.

Could you type in adb shell (or terminal) and post the output:

im trying to get adb running but it just runs then disappears

 

[hlxanthus]

In windows on a pc, go to the start menu and into the search programs and files type "cmd" which will find the cmd.exe. Open that up and type adb shell. And make sure phone is pluged in of course with debugging mode on and usb mass storage off.

 

[djsanchez5]

gRom should be pre-rooted. If that is the case, it should be very simple to get xionia back on.

Could you type in adb shell (or terminal) and post the output:

C:\AndroidSDK\platform-tools>adb shell
~ # /system/bin/ls -l /system/bin/su
/system/bin/ls -l /system/bin/su
/sbin/sh: /system/bin/ls: not found
~ #

 

[djsanchez5]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\SANCHEZ>adb shell
'adb' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\SANCHEZ>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\SANCHEZ>cd\

C:\>adb shell
'adb' is not recognized as an internal or external command,
operable program or batch file.

C:\>cd androidsdk

C:\AndroidSDK>platform-tools
'platform-tools' is not recognized as an internal or external command,
operable program or batch file.

C:\AndroidSDK>cd androidsdk\platform-tools
The system cannot find the path specified.

C:\AndroidSDK>cd platform-tools

C:\AndroidSDK\platform-tools>cd adb
The system cannot find the path specified.

C:\AndroidSDK\platform-tools>adb
Android Debug Bridge version 1.0.29

-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.

If -p is not specified, the ANDROID_PRODUCT_OUT

environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments

will disconnect from all connected TCP/IP devic
es.

device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport

adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.

adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)

adb restore <file> - restore device contents from the <file> backup
archive

adb help - show this help message
adb version - show version num

scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:

- If <directory> is not specified, both /system and /data partitions will be u
pdated.

- If it is "system" or "data", only the corresponding partition
is updated.

environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.

C:\AndroidSDK\platform-tools>adb devices
List of devices attached
A0000028C8375C recovery


C:\AndroidSDK\platform-tools>adb shell
~ # /system/bin/ls -l /system/bin/su
/system/bin/ls -l /system/bin/su
/sbin/sh: /system/bin/ls: not found
~ #

 

[hlxanthus]

Am I reading that right? That is script of you trying just to get adb to run? If you ran gingersnap before in you attempts to root, adb should be installed and the proper command paths set. Just go to cmd.exe and type adb shell.

Sent from my LS670 using Tapatalk

 

[sfhub]

C:\AndroidSDK\platform-tools>adb shell
~ # /system/bin/ls -l /system/bin/su
/system/bin/ls -l /system/bin/su
/sbin/sh: /system/bin/ls: not found
~ #

Are you doing this while booted into Recovery (ie your "blank screen") or Android?

It seems you have root already (denoted by the "#" sign in your prompt)

Do the same commands while booted into Android instead of Recovery or just type "su" in adb shell and look for a prompt that shows up on the phone's screen.

If you can get a "#" prompt when booted into Android, then we can have you fixed up pretty quick.

 

[djsanchez5]

heres the thing when i boot the phone i get the lg logo the straight black screen. im getting a headache. its not letting me <dir> to the sdcard.
so i take it theres no way to re-flash the software without doing all of this.

 

[sfhub]

How did you get the Android Screencast image you posted above? Is that with the blank screen or is that when the screen is showing something?

 

[djsanchez5]

How did you get the Android Screencast image you posted above? Is that with the blank screen or is that when the screen is showing something?

Thats from thr blank screen. Screencast keeps showing those pics i posted above

 

[sfhub]

So when Android Screencast shows the optimus2.jpg picture (the first picture), could you type in "adb shell"

mount
ls -l /system/bin
ls -l /system/app