If you would Like to Pull a File / App. First we would do this....
Quote:
adb shell
cd /system/app
ls -l
Now we should have a Huge amount of App's in front of us, now we locate the name of the App we wish to pull Once we Find it, we do the Following.. ( In this example I'll be Pulling the alarmclock.apk )
Next, If still in Command Prompt.
Quote:
exit
running exit will drop you back into Command prompt shell, From there we Running the Following Commands in Blue...
adb pull /system/app/AlarmClock.apk C:\AlarmClock.apk
Now we should have the alram clock app in our Root Directory in C:\
Now to Push the alarm clock app after we made changes to it...
I have tryed to get this going for a few days now with no luck. I have tryed different drivers all ran with signed drivers disabled. I've tryed a few cables and 3 different machines. Everytime i type in adb shell it says device is offline. I type in adb devices and it shows t939 device offline. I have usb debugging on and it set to samsung pc studio mode. i want bhmans rom badly... im not even gonna get this fabled update anyways. any help would be very much appreciated.
P.S. i use win7 64bit ultimate, My other 2 machines are running winxp pro and win 2000.
i found it much easier to use windows xp. so you do have the avd installed correct? i was having problems for a while too then i finally got it. also make sure ur device isnt in usb mass storage mode so when you plug in via usb dont mount. hope this helps if not let me know
You need to download the sdk or the tools.rar. Extract it and cd to the tools directory. Then run adb.
Here's the tools directory you need including abd and the driver (windows should ask you for it when you turn on usb debugging and turn off mass storage mode)
How do you do it and what is needed I can not get my device to show up when I type adb shell. I download the android files from google but im stuck this is a big jump from my windows mobile world.
Would love some help people thanks to all.
Then you must install the drivers for the Behold 2. Drivers can be found in the following file http://shrunk.me/uvij6.zip
That file also include the ODIN files which allow you to flash back to completely stock (out of factory) for your phone. For ODIN instructions please reference this post: {PORT} Behold 2 Stock ( No Twiz w/ Root & Busybox )
Now when you plug-in the phone via the USB, it will ask to install drivers and point them to the Behold 2 drivers.
Assuming that you are running the stock Touchwiz you must put your phone into a mode that adb will work. On Touchwiz you go to Settings>>Application Settings>>Development>>USB Debugging (put a check mark). Then go to Settings>>Phone Settings>>USB Settings>>Samsung PC Studio, click SAVE. It should then install the ADB drivers. If not toggle between Mass Storage, click Save then click Samsung PC Studio and click save.
Open a command prompt windows (Start>>Run>>CMD) then
Code:
cd c:\android-sdk-windows\tools
adb shell
This will get you the adb shell onto the device, allowing you to enter the commands to install the MOD.
Make sure to extract the files from BH_Man onto the root of your SDCARD and make sure its then mounted on the phone. Good Luck.
The Following User Says Thank You to Mastermind278 For This Useful Post:
One other thing I have noticed is that if you have an alternate Home - ie @Home, Home++, SweeterHome, etc you will not be able to get ADB to work until you are using the stock TW home.
ok so its probably been posted many many times and i know this because i have read 2 post on here and many other post from different web sites and i have read and tried so many times im fed up and really want this to work.
I have done everything to a T to try and get this working with a no working status happing.
SO IF THERE IS ANY ONE OUT THERE HAVING THIS SAME PROBLEM AND FIXED IT please please email me or post reply.
i have tried uninstalling drivers reinstalling. i have reset phone. i have done every thing possible in my right mind from reading to try and get it recognized by adb but still cannot
Do not have any of those things like I said I did a factory reset on it just to make sure. Yes I can mount as removable drive. I'm also using windows xp 32bit.
I mean I just don't freakin understand why its not working.
I sat there for 4 hours yesterday trying to get recognized by adb....
I am savy with these things computers phones blah but I just can't figure this one out
I am no tech guy thats for sure, but when you plug your phone to your cpu dont mount it set the phone settings to studio then start up cmd and make sure you got debugging on that did it for me. Since I got this thing rooted it has been great, so push on man it is really worth it
I am no tech guy thats for sure, but when you plug your phone to your cpu dont mount it set the phone settings to studio then start up cmd and make sure you got debugging on that did it for me. Since I got this thing rooted it has been great, so push on man it is really worth it
I donot mount the question asked before was does it mount as in are the usb drivers working.. I said yes. And i know its worth it just cant get the behold to be recognized which is making me mad.
I have downloaded the manual drivers still nothing. is there any information for any of the tech guys here that they need to see what the problem is.. DXdiag? phone version firmware version so on?
Device(s): G1(with all the tricks & hacks) , Behold2 , Vibrant(rooted stock 2.1)
Carrier: Not Provided
Thanks: 1
Thanked 22 Times in 15 Posts
did you un_check mass storage , when you go to >about phone>additional settings ? that's the only other one there is , you can also press n hold the call button and say phone 'status' to get this menu . ...
did you un_check mass storage , when you go to >about phone>additional settings ? that's the only other one there is , you can also press n hold the call button and say phone 'status' to get this menu . ...
found the setting but now when i usb it only charges no connection ill try uninstalling drivers then reinstalling but well see
if i'm reading correctly, my phone did the same thing (just charges and doesn't connect). Then i went into the notification bar (while plugged in), went into phone and USB settings. It was already set to PC Studio so i just pressed save and it reset the usb connection and adb recognized it.
khunny7@khunny7-x60s:~$ adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
khunny7@khunny7-x60s:~$ lsusb
Bus 001 Device 013: ID 04e8:6603 Samsung Electronics Co., Ltd
Bus 001 Device 012: ID 0c45:62f0 Microdia
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
khunny7@khunny7-x60s:~$
I think I did pretty much everything that some of the references told me to do.
I wonder what my problem is.
Can anybody help me?
I just installed BH_Man's (Port) Behold 2 1.6 Factory w/ Busybox & Rooted Kernel and am trying to get the Camera fix to work. However when I type in
Quote:
adb push C:\Documents and Settings\Compaq_Owner\Desktop\Camer_16_Fix /system/app
I get
Quote:
Android Debug Bridge version 1.0.25
-d - directs command to the only connected USB device
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 running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
envivornment 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
disconnect <host>:<port> - disconnect from a TCP/IP device
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
(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] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
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 help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
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 specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
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 the 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 updated.
- If it is "system" or "data", only the corresponding partition is updated.
Which I'm assuming is the 'user manual'. What am I typing wrong?
Because of the way your are placing the command in the box you have 2 choices:
a) adb push "C:\Documents and Settings\Compaq_Owner\Desktop\Camer_16_Fix" /system/app
OR
b) copy the Camer_16_Fix to the same folder where ADB is and then run the command this way:
adb push Camer_16_Fix /system/app
The problem:
Because of the C:\Documents and Settings\Compaq_Owner\Desktop path, DOS will interpret that each word is a command, that's why you have to include the "" at the star and end because its the only way you cant tell the OS that you are dealing with one full string.
Choose what works for you best, and let us know.
The Following User Says Thank You to megabiteg For This Useful Post:
Because of the way your are placing the command in the box you have 2 choices:
a) adb push "C:\Documents and Settings\Compaq_Owner\Desktop\Camer_16_Fix" /system/app
OR
b) copy the Camer_16_Fix to the same folder where ADB is and then run the command this way:
adb push Camer_16_Fix /system/app
The problem:
Because of the C:\Documents and Settings\Compaq_Owner\Desktop path, DOS will interpret that each word is a command, that's why you have to include the "" at the star and end because its the only way you cant tell the OS that you are dealing with one full string.
Because of the way your are placing the command in the box you have 2 choices:
a) adb push "C:\Documents and Settings\Compaq_Owner\Desktop\Camer_16_Fix" /system/app
OR
b) copy the Camer_16_Fix to the same folder where ADB is and then run the command this way:
adb push Camer_16_Fix /system/app
The problem:
Because of the C:\Documents and Settings\Compaq_Owner\Desktop path, DOS will interpret that each word is a command, that's why you have to include the "" at the star and end because its the only way you cant tell the OS that you are dealing with one full string.
I removed TwMms.apk fine from the bh_mans behold 2 1.6 no touchtiz. But I could not get the Mms.apk to install until I followed behold_this's rules. It seemed to install just fine, but now everytime I open it, it immediately closes. I don't even get a force close screen. It just shuts down before the page even comes together. I'm not sure what the problem is. On a side note I seem to have been having texting problems all weekend. (I just removed TWMms.apk today), but apparantly people say they have been sending messages to me, and I got a total of ZERO all weekend.
Any suggestions?
How-to Thread For ADB SHELL
Adb shell and devices says device offline
)
