Related
I dont want to install linux for this one purpose of fixing my lcd density so i downloaded a live cd of ubuntu. Is there a way to use adb on here i tried one way and i had to extract files to the usr/bin which it wouldnt do ( i think because that exists on the disc so its not able to write) any help? maybe another way for adb on linux so i can fix that build.prop?!
you could run it in terminal:
in the adb's folder, run:
Code:
./adb [your command]
hey
i got the adb running the way u said to with adb in the folder. it still dose not show my device and my phone is in debug mode also. on linux it doesn't even show my sd card.
i put in abd devices and no device is shown. any help did i miss a step here.
I kinda have the same problem, I'm new to linux, and just finished installing Ubuntu on my laptop. The first thing I was thinking whether i needed a driver to install the phone like in Windows, or is there some "device manager" like plugin to find out more details on what devices need drivers or whats installed.
on my kaiser, adb doesn't work always. reboot your android if not.
You could see it with command:
Code:
lsusb
and/or
Code:
adb devices
hey thanks dark side just got a hero and couldn't be happier except for battery life my old vogue lasted longer lol (probably all the hero HTC stuff). But thanks for actually giving advice about the adb! no one else seemed to it drove me to get a hero! The sense ui is really great i didn't think i would like it because of how it felt on vogue. but actually its a really good thing. That sense ui from jamezelle is insane. its almost like it but after u leave an app it dose not loads again. if he some how gets that fixed it will be close to the hero. anyway everyone thanks for letting me experience android (dzo plemen, jamezelle and zen i tired your builds so this is to you). You helped with my decision to get a hero. Best phone i have ever owned! also to help anyone i think that if u plug your phone into windows 7 and then windows xp it can mess up your adb with the vogue that what happened to me... it let me see the files in windows 7 but after i hooked up to xp both became unable to use!
http://adoxa.110mb.com/ansicon/index.html
Something I found awhile back to enable colors in windows shell, after you open cmd, run ansicon then do your adb shell and you get colors instead of junk text.
Also I love adbWireless from the market, no having to dig out my USB cable to use adb, even push files over without usb cable
Thanks, I was looking for it
wow how did i not find out about adbwireless earlier, this tool is fantastic!
IStern said:
wow how did i not find out about adbwireless earlier, this tool is fantastic!
Click to expand...
Click to collapse
then tell me you know about appbrain.com and also their fastweb installer? you click install on their site, the permissions dialog pops up like on the phone, you hit ok and go to your phone in a minute and its already installed
I've just about given up. I downloaded all these programs, drivers, other stuff. I thought I had all the required software. I tried to run adb.exe and it just opens a command prompt and closes right away. I've tried searching and all the guides says download this....this..and this..once you have it all. And it starts from there.
The problem is i downloaded everything and I don't know if its working properly to start adb.
I hate this.
I've even thought about downloaded a whole other OS and running it from my USB drive to see if it's easier.
Anyone know of a good how to video?
I know that's what i'll be making as soon as I get this up and running.
Are you actually running adb through a command prompt or just double clicking the exe?
Sent from my T-Mobile G2 using XDA App
CMP
take a look.
http://www.youtube.com/watch?v=-rTOy5oN0GM
use cmd to run it
Start -> Run -> Type cmd -> Enter
cd whatever/directory/adb.exe/is/in
adb
you should just add the android tools directory to your PATH makes life much easier.
Sent from my T-Mobile G2 using XDA App
Yep editing the path got it to work for me.
Sent from my T-Mobile G2 using XDA App
They are aren't they? The vid shows them in there.
Sent from my T-Mobile G2 using XDA App
if you are having that much issue setting the correct path, just go to your system 32 and copy over the CMD.EXE to the folder you are working in with Android. And then launch CMD from there.
Or just type into command prompt
PATH = %PATH%;C:/Android/Folder/Youre/Working/With/
EDIT:
I just watched your video. You have some problems in there
First, you aren't setting a new path, you are (attempting) to change your working directory in that video, however you are not doing it right.
You have to use the 'cd' command
C:\Current\Work\Space > cd C:\Change\to\this\space
C:\Change\to\this\space > adb devices
bleh bleh bleh bleh
But it would be better to just do the above method.
In most cases, the instructions are pretty clear. If you read the instructions on installing the SDK, it tells you how to set the path.
http://developer.android.com/sdk/installing.html
If you follow instructions, then you should be good to go.
If not, then you should be able to do something like a google query for "set path variable windows < whatever kind of windows you're running >"
If you're having a problem getting that stuff done, then maybe you should rethink rooting your phone. I don't know that anyone has bricked a G2 yet, but LOTS of folks bricked G1s. I think it's only a matter of time before someone figures out how to thoroughly break a G2.
"Just to add, if you take adb.exe and adbwinapi.dll and copy or move them to the \windows\system32 directory you can run adb from any dos directory prompt."
Also, add the "ADB" directory path as a system variable in windows...
To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista) then select Environment Variables.
Click "New" under System Variables and add the following:
Variable: adb
Value: C:\android\tools
If you happen to upgrade to Win7 you can easily open the CMD by shift right-click inside the window itself.....applying the path automatically for you.
You will also have too use these drivers located here: http://forum.xda-developers.com/showthread.php?t=802316
or
Use notepad++ to edit that file and add the following lines to the "google.ntxhe "" and the "google.ntamd64" sections:
Code:
;T-Mobile G2 %SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91 %CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91&MI_01 ;
Save the file, reinstall drivers, and done...
Click to expand...
Click to collapse
smasraum said:
In most cases, the instructions are pretty clear. If you read the instructions on installing the SDK, it tells you how to set the path.
http://developer.android.com/sdk/installing.html
If you follow instructions, then you should be good to go.
If not, then you should be able to do something like a google query for "set path variable windows < whatever kind of windows you're running >"
If you're having a problem getting that stuff done, then maybe you should rethink rooting your phone. I don't know that anyone has bricked a G2 yet, but LOTS of folks bricked G1s. I think it's only a matter of time before someone figures out how to thoroughly break a G2.
Click to expand...
Click to collapse
Thanks, looks like I'll be waiting it out. I didn't think it took this much know how to get sdk and adb running properly. I was able to change the path but ran into another brick wall. I type in abd devices to see if it was recognized and nothing. Like i said, I'll be waiting it out until a more permanent route can be found, and more support for rooting is available. Besides I don't think anyone wants to hold my hand and walk me thought the whole thing. It gets annoying, believe me I know. I'll be doing a how to video once I learn to get it all working and when a permanent root is available. I'll learn on XP and make the video using my Win 7.
ddgarcia05 said:
Thanks, looks like I'll be waiting it out. I didn't think it took this much know how to get sdk and adb running properly. I was able to change the path but ran into another brick wall. I type in abd devices to see if it was recognized and nothing. Like i said, I'll be waiting it out until a more permanent route can be found, and more support for rooting is available. Besides I don't think anyone wants to hold my hand and walk me thought the whole thing. It gets annoying, believe me I know. I'll be doing a how to video once I learn to get it all working and when a permanent root is available. I'll learn on XP and make the video using my Win 7.
Click to expand...
Click to collapse
The G2 isn't included in the current adb drivers that you download separately/with the SDK. You have to edit the inf file to have the G2 recognized. There has been at least 1, maybe a few threads with the lines to add here. I think there's a thread titled something like "I can't get adb to work with my phone" or something like that.
looks like i was doing it right. I was typing "abd" instead of 'adb" it founy device.
Now I guess the have to start sending the files over....
I typed "adb devices" and it picked up my device. with my phone's id number.
I am also about to give up. Some of us are new to Android.. we don't understand SDK and ADB and all these other programs. I do plenty enough reading.. but for some reason can't get these programs to run on Windows 7 x64.
I mean is their a newbs guide for the G2.. for rooting and such?
Yeah there is but you have to read like three guides and watch two videos to fnd everything you need. Ill try to make a quick how to after I finish up mine. I just have to push the apps/install the apps. Did you find the java jdk version. And do the commands on your computers cmp?
Sent from my T-Mobile G2 using XDA App
I always used this guide:
[GUIDE] ADB, Fastboot, and Nandroid for Noobs
Hope it helps
Use the drivers in post 11 in this thread
Unless you rooted your G2.........adb shell will NOT work.
ADB shell needs root access
Thanks, I have already rooted my phone. Unfortunately my wifi tethering doesn't work. It always says no network access so I'm just going to leave the phone as is until the update comes in.
Sent from my T-Mobile G2 using XDA App
ddgarcia05 said:
Thanks, I have already rooted my phone. Unfortunately my wifi tethering doesn't work. It always says no network access so I'm just going to leave the phone as is until the update comes in.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
why not use VISIONary app to root the phone for you?
konoplya said:
why not use VISIONary app to root the phone for you?
Click to expand...
Click to collapse
At the time it wasn't available, but I'm using it now.
I am trying to get a development environment setup and running into all sorts of problems with ADB when I have an actual device attached to the system. I am using eclipse and can use the emulators with no problems, until I attach an actual device to the system. At that point, even when trying to debug on the emulator, ADB keeps crashing. I can start a debug session on the actual device, but if I try to switch to the DDMS view, ADB crashes.
I am running on windows 7 and have even go so far as to do a complete reinstall of the system and only install the development tools only to have this problem show up again. I can't believe that this is normal, how could anything get developed with this type of issue?
I have been searching for answers and not been able to find anything helpful. I restart ADB only for it to immediately crash again. All the software is updated to the most recent versions. This problems occurs on both my desktop and laptop so don't think it is a hardware issue with my systems. Only thing really in common is the device, my EVO.
Any help would be appreciated. This is driving me nuts. I need to get this working for some projects but I feel like I am pounding my head on a brick wall trying to get it to work.
If this isn't the best place for this thread, could you please point me in the right direction? Thanks.
First navigate to where adb is located within cmd prompt.. [depends on what tutorial you followed if any at all] Either C:\android-sdk-tools\tools or if you used the .exe installer then itll be in your Program Files\android\android-sdk-tools\platform-tools\.. when you are in the directory of the adb location in cmd prompt runt the following code.. "adb devices" to see if adb is working at all.. it sounds like it might be a ROM issue unless adb is missing files it needs which i ran into that problem.
jr10000 said:
First navigate to where adb is located within cmd prompt.. [depends on what tutorial you followed if any at all] Either C:\android-sdk-tools\tools or if you used the .exe installer then itll be in your Program Files\android\android-sdk-tools\platform-tools\.. when you are in the directory of the adb location in cmd prompt runt the following code.. "adb devices" to see if adb is working at all.. it sounds like it might be a ROM issue unless adb is missing files it needs which i ran into that problem.
Click to expand...
Click to collapse
ADB is working fine like this. My phone shows up in the devices command. I can shell to it. Push/Pull files. All with no problems. It's not until I try running a debug session from eclipse (either in the emulator or on the device) that it crashes.
No one here that can help?
To the best of my knowledge, you either use the Emulator OR the phone.
At least that's what I do. Before I plug in my phone, I shut down any Emulator(s) that I might be running.
Also make sure to eject phone (Mac) or stop the device (Windows).
Never had a problem.
Rootstonian said:
To the best of my knowledge, you either use the Emulator OR the phone.
At least that's what I do. Before I plug in my phone, I shut down any Emulator(s) that I might be running.
Also make sure to eject phone (Mac) or stop the device (Windows).
Never had a problem.
Click to expand...
Click to collapse
The problem is I can't use EITHER when the phone is connected. So even if I wanted to debug on the phone, I can't.
i have the same problem, and it drives me crazy, i can't get a specific reasong, once i uninstalled google upadter and the adb works fine, second time i uninstalled Google chrome and it work fine until yesterday, today it is back to crashing, i dont know what else to do
Edit: my problem started after upgrading to android 2.3
NoEnd said:
i have the same problem, and it drives me crazy, i can't get a specific reasong, once i uninstalled google upadter and the adb works fine, second time i uninstalled Google chrome and it work fine until yesterday, today it is back to crashing, i dont know what else to do
Edit: my problem started after upgrading to android 2.3
Click to expand...
Click to collapse
I have pretty much given up on getting it to work right. I have a linux box that I set up the development environment on and it is working fine there. I'm thinking it could be something with 2.3 also. Going to see if I can find the 2.2 and do the setup with that.
edboston said:
I have pretty much given up on getting it to work right. I have a linux box that I set up the development environment on and it is working fine there. I'm thinking it could be something with 2.3 also. Going to see if I can find the 2.2 and do the setup with that.
Click to expand...
Click to collapse
Try going into your sdk/tools folder and setting adb to run as administrator, expecially for win 7 (leave it open then go back to eclipse). I had the same problem and I also closed the emulator when debuging on the device.......don't know, but maybe it will work for you also. Good luck!
awrnsmn said:
Try going into your sdk/tools folder and setting adb to run as administrator, expecially for win 7 (leave it open then go back to eclipse). I had the same problem and I also closed the emulator when debuging on the device.......don't know, but maybe it will work for you also. Good luck!
Click to expand...
Click to collapse
No luck. Eclipse reported it couldn't run adb because it needed elevated. Thanks for the suggestion.
yeah tell me when ever found a soultion for the problem, it seems that it's a small problem
is your windowsOS 64??
NoEnd said:
yeah tell me when ever found a soultion for the problem, it seems that it's a small problem
is your windowsOS 64??
Click to expand...
Click to collapse
Yes it is. But I do have the 32bit version of all the development system. I have an extra drive on my system that I can try installing the 32bit version of Windows 7 on and see if I have any better luck with that.
edboston said:
Yes it is. But I do have the 32bit version of all the development system. I have an extra drive on my system that I can try installing the 32bit version of Windows 7 on and see if I have any better luck with that.
Click to expand...
Click to collapse
please do and reply back
NoEnd said:
please do and reply back
Click to expand...
Click to collapse
Just tried running it on 32bit windows. Same problems. ADB crashing.
edboston said:
Just tried running it on 32bit windows. Same problems. ADB crashing.
Click to expand...
Click to collapse
there must be a problem with the phones???
mine is Desire HD
Rom Revolution HD
NoEnd said:
there must be a problem with the phones???
mine is Desire HD
Rom Revolution HD
Click to expand...
Click to collapse
I had someone suggest it could be a custom rom or kernel issue. I am running an evo with a custom rom and kernel. I'm not sure where the adb part is implemented but I might be able to try stock later this week. Strange that it works fine on my linux box with the custom. Probably the linux version of adb is more robust and can handle the errors better.
I'm having similar issues on Windows 7 32 and 64 bit. I'm using the 2.3 tools.
The interesting thing is that ADB only crashes when I try to run (not debug) one particular application (one I wrote) inside Eclipse. I have 3 other projects that work just fine, no crashing.
Even with the one app, it starts out working ok, then it'll start crashing when I try to run it, and then it'll crash anytime eclipse is up and that program is running on the phone!
Completely wiping the data partition fixes it for a while, but that's obviously a crappy solution.
Wiping the Cache/Dalvik Cache doesn't do anything.
Wiping the data for the com.android.debugtool (is this even related to ADB? seems too coincidental) doesn't do anything.
Uninstalling, or just killing my app on the phone, stops the crashing, until the program is installed, or starts, again.
Turning off and on USB Debugging a few times seems to sometimes help, but only for a while.
Rebooting also can help stop the crashing for a while, but not every time.
I turned the logging in eclipse up to verbose, but I don't see anything in the console window that seems to offer any clues.
Is the problem with ADB, or with DDMS? (DDMS is what eclipse runs to do everything on your device, DDMS then calls ADB). Because without eclipse open, adb works fine. Or is it a specific command send to ADB through DDMS? Is there any way to find out exactly what DDMS is doing with ADB?
Does anyone know if there's another "debugging" cache on the phone somewhere that, if cleared, may fix the crashing?
Scott
edboston said:
I had someone suggest it could be a custom rom or kernel issue. I am running an evo with a custom rom and kernel. I'm not sure where the adb part is implemented but I might be able to try stock later this week. Strange that it works fine on my linux box with the custom. Probably the linux version of adb is more robust and can handle the errors better.
Click to expand...
Click to collapse
Okay. Tried it with the stock ROM/Kernel with the same results. ADB crashing.
Delvorak said:
I'm having similar issues on Windows 7 32 and 64 bit. I'm using the 2.3 tools.
The interesting thing is that ADB only crashes when I try to run (not debug) one particular application (one I wrote) inside Eclipse. I have 3 other projects that work just fine, no crashing.
Even with the one app, it starts out working ok, then it'll start crashing when I try to run it, and then it'll crash anytime eclipse is up and that program is running on the phone!
Completely wiping the data partition fixes it for a while, but that's obviously a crappy solution.
Wiping the Cache/Dalvik Cache doesn't do anything.
Wiping the data for the com.android.debugtool (is this even related to ADB? seems too coincidental) doesn't do anything.
Uninstalling, or just killing my app on the phone, stops the crashing, until the program is installed, or starts, again.
Turning off and on USB Debugging a few times seems to sometimes help, but only for a while.
Rebooting also can help stop the crashing for a while, but not every time.
I turned the logging in eclipse up to verbose, but I don't see anything in the console window that seems to offer any clues.
Is the problem with ADB, or with DDMS? (DDMS is what eclipse runs to do everything on your device, DDMS then calls ADB). Because without eclipse open, adb works fine. Or is it a specific command send to ADB through DDMS? Is there any way to find out exactly what DDMS is doing with ADB?
Does anyone know if there's another "debugging" cache on the phone somewhere that, if cleared, may fix the crashing?
Scott
Click to expand...
Click to collapse
your reply can be summarize in few points:
1- its a library or code you used in that app that crashes ADB.exe (as u said only this app)
2- it maybe an app in the phone, the apps i suspect is SU(for rooted phones) or Whatsapp(because it's runs a service that stops as soon as the USB mode activated)
i hope this Thread doesn't die, because it's the only one on the WEB.
One thing I checked between the v7 and v8 of the SDK is adb.exe is the same version in each of these. So the thought about the DDMB being a possible culprit is a good possibility. Because outside of eclipse debugging, I have no problems with ADB at all.
So I have a bit of an issue. Somehow last night, after trying to help my parents with our home theater system, with the device laying on a soft surface, the LCD (not the glass) somehow broke. I am really not sure how this happened, the phone itself didn't fall, it was laying on a bed the entire time. When I went to grab the phone and turn it on, I was pretty surprised. You can see what I mean in the attached file.
Now the problem with this is, while I would normally just walk into the Sprint Store, complain and get a new phone. I am not in the US for another 5 months. In the mean time of trying to figure out what to do, I would like to at the very least, grab any files off my phone, or back up my phones' file structure.
I am able to do a minimal amount of tapping on the phone, only on the upper half of the screen, but I can't see anything, nor does the device respond with any touch data from the bottom half.
I obviously can't access the files if the device is locked, which means I have to bypass the lock screen. I found this guide, but unfrotunately, Method 1 didn't work, and I can't get adb to recognize my phone for Method 2.
I also have tried using CWM (the non-touch version) to backup my data, but I let it sit there for 45 minutes and I couldn't tell if it was finished or not. It didn't appear to actually be doing anything.
Could someone help me navigate around this or provide some assistance in allowing me to just get the files off the phone while I search for a new one?
With that being said, does anyone have some recommendations? I was thinking of getting a Motorola X or Nexus 5.
EDIT: Update:
I have access to terminal via Cerberus shell. I was able to use Method 2 to disable the lock screen (or in this case set it to Swipe). It is still pretty difficult to use the phone but I can at least backup whatever data I still do have on the phone to my laptop.
Would anyone be able to give me some advice as to uninstall applications or XDA xposed modules via shell? Or perform a backup or enable ADB debugging?
You've conntected to your PC at least once so that the ADB has permission, correct? If so, you can get http://forum.xda-developers.com/showthread.php?t=2786395 to get Android Control and view/Control your phone via USB. You need to have Java installed, which most have already. Been controlling my cracked LCD for the past week while waiting for my replacement.
Keep in mind this method is a little slow because of ADB. Hopefully you don't have to type too much.
Darnell0216 said:
You've conntected to your PC at least once so that the ADB has permission, correct? If so, you can get http://forum.xda-developers.com/showthread.php?t=2786395 to get Android Control and view/Control your phone via USB. You need to have Java installed, which most have already. Been controlling my cracked LCD for the past week while waiting for my replacement.
Keep in mind this method is a little slow because of ADB. Hopefully you don't have to type too much.
Click to expand...
Click to collapse
I know I have connected it at least once, but when connecting the phone and the pc together, adb cannot find the phone. I am not sure if this is because of a Cerberus setting (that disables debugging) or something else. I will give it another shot when I get home.
If I can't, is there any way for me to somehow accept the adb permissions on the phone via a command versus touching the screen? Say if I have shell access over Cerberus and adb access from my PC?
slixzen said:
I know I have connected it at least once, but when connecting the phone and the pc together, adb cannot find the phone. I am not sure if this is because of a Cerberus setting (that disables debugging) or something else. I will give it another shot when I get home.
If I can't, is there any way for me to somehow accept the adb permissions on the phone via a command versus touching the screen? Say if I have shell access over Cerberus and adb access from my PC?
Click to expand...
Click to collapse
There's a bit of work to push the ADB acceptance key if you have a spare android phone lying around. Other than that, there probably is but might be more of a headache. I took the ADB key for my desktop from another android and pushed it in through TWRP which accepts ADB commands while in Recovery.
Darnell0216 said:
There's a bit of work to push the ADB acceptance key if you have a spare android phone lying around. Other than that, there probably is but might be more of a headache. I took the ADB key for my desktop from another android and pushed it in through TWRP which accepts ADB commands while in Recovery.
Click to expand...
Click to collapse
I have a sony xperia P that I am using right now until the replacement phone I got arrives. Any idea how I could use that? I have had minimal success with the phone so far in trying to get that phone to flash custom recoveries, to root the device (not sure why, but my laptop just doesn't want to seem to do it, even using automated tools).
Is it better to just wait for the replacement phone to arrive and grab what I need from that and push it? Could you link me to any guide or steps that you used with yours?
Thanks for such quick responses by the way!
EDIT:
Flashing TWRP and booting into recovery with command prompt open and running adb devices / fastboot devices does not show any devices available.
Is there a specific menu setting or other option I need to use to be able to run adb?
When you use TWRP, the phone will be recognized by the PC but the driver doesn't install correctly off the bat. Go to Device Manager and look for your phone. You may need to click the View -> Show Hidden Devices option. Update the driver manually by selecting the one provided by your manufacturer. Some have a dedicated ADB driver for specific functions (bootloader, etc).
The adb key is stored in data/misc/adb/adb.keys -You can pull this file from any other android connected to that PC (or just copy it if you have a root explorer) and push it to the broken one if necessary. This will bypass any ADB authorization issues while the phone is fully booted and let you see the screen.