I installed ADB (Windows 7) has described in this forum. ADB recognizes my phone when the phone is on. When I load the bootloader to prepare to unlock it the serial number does not show like when its on. Is this normal? Do I just proceed to unlock it?
Sent from my Nexus S using XDA App
sarge363 said:
I installed ADB (Windows 7) has described in this forum. ADB recognizes my phone when the phone is on. When I load the bootloader to prepare to unlock it the serial number does not show like when its on. Is this normal? Do I just proceed to unlock it?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You should not see it mounted unless you have it mounted. try running this command replacing blah with the file path to your adb file
Code:
blah/blah/blah adb shell
If it works, you're golden. If not, troubleshoot
I set the environmental variables so I can just enter adb shell?
Sent from my Nexus S using XDA App
sarge363 said:
I set the environmental variables so I can just enter adb shell?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Um I'm not too great with windows and on a mac we just drag the adb file into our command prompt and it works =/ what I'm saying is I have no idea what you mean by environmental variables. Try it? If it doesn't tell you the phone isn't there but also doesn't say its starting the daemon then you have to enter everything.
Awesome I'll give it a shot when I get home.
Sent from my Nexus S using XDA App
I tried adb shell and it says error: device not found. I've tried to update the drivers that i got from this thread.
http://forum.xda-developers.com/showthread.php?t=878786
Inside the x64 drivers there looks like there are 4 that might work:
Android_test
Android_usb
Android_winusb
Android_winusb2
I really dont understand what I'm doing wrong.
Edit: I entered the entire path and still nothing.
haha I got it. I was getting frustrated of trying to "play it safe" and said screw it. I just went ahead and entered fastboot oem unlock and it worked lol......
Rooted!!!
Sent from my Nexus S using XDA App
Congrats
Sent from my Nexus S using XDA App
I want to be able to use adb to pull/ push apps to my phone.
I recently converted my PC to Ubuntu 10.10 from windows and I am finding it impossible to find any sort of noob friendly guide as to how I can actually get it installed and working.
Can anyone help? Or point me towards a guide. All the stuff I find seems to assume you either already have it installed or know how to do it already!
Sent from my GT-I9000 using XDA App
Well thanks for your help folks
Sent from my GT-I9000 using XDA App
here ya go http://tinyurl.com/44zscrd
Follow the first guide, if you still have problems post back and I'll try to help you with what you need
Ok I tried this, I realise you were taking the piss but the guide was good except I could not get Ubuntu to recognise my device. Followed the instructions to the letter. I know Linux is not meant to be easy but why is it SO hard?
Sent from my GT-I9000 using XDA App
branalvere said:
Ok I tried this, I realise you were taking the piss but the guide was good except I could not get Ubuntu to recognise my device. Followed the instructions to the letter. I know Linux is not meant to be easy but why is it SO hard?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
ubuntu recognizes it by default unless you modified your settings or messed with the kernel.
http://developer.android.com/sdk/index.html
Download the Linux tools. Extract it then open your terminal and go to the extracted folder, inside here is a folder called tools, with the terminal cd into tools and type ./android.....app should open, go to available packages, android repository, check the first one and should be android sdk tools.
Click install selected at the bottom right. Once it's done you will have adb installed.
On your phone, go to settings, applications, development, check usb debugging. Also check unknown sources.
Inside the folder you are in, there should be a file/ script called adb. This means you can run the adb commands from here.
In terminal, assuming you are in the folder where the adb file is located, type:
Sudo ./adb start-server
This should recognize your phone.
This incorporates the ideas of http://forum.xda-developers.com/showthread.php?t=2144709, so if you want to see how this was resolved for the Nexus 4, check out that thread.
Okay. So you've flashed a spanking new 4.2.2 ROM and ADB no longer talks to your Sensation. What happened?
Well, the fact is that 4.2.2 is significantly more secure, in the good sense. It enforces RSA authentication via ADB. However, RSA authentication is supported only in recent versions of ADB.
What to do?
First, make sure you have the latest version of ADB on your PC.
On Windows you can quickly find out if you your version of ADB is up to date. Check your ".android" folder and see if it holds a file called "adbkey".
On any platform type "adb version" to verify that you have the latest version of ADB. Versions 1.0.31+ support RSA authentication.
-- So now, if you have ADB 1.0.31 or higher. You can skip directly to step 2, then.
-- If you do not have ADB 1.0.31 or higher, and you have the full Android SDK installed, open the SDK manager and update it. If you only have ADB and fastboot installed in a folder on your PC, overwrite files in the folder with those in the corresponding zip file attached (windows or linux -- sorry! I don't have Mac versions at this time). These come from version 16.01 of the android platform-tools package, if you are curious.
-- if you have never installed the SDK or ADB or fastboot, now is the time to do that. I recommend going to http://developer.android.com/sdk/index.html to get started.
[*]Enable USB debugging on your phone
USB debugging is now enabled by selecting Android Debugging in System Settings > Developer Options.
"I don't have the Developer Options items in System Settings!!"
In Android 4.2.x, you need to go to System Settings > About Phone and tap the Build Number item about 6 or 8 times, and Developer Options will reappear.
[*]Plug in the USB cable. Securely.
Dismiss the USB mass storage window.
"I connected the cable, but nothing happened!!"
Okay, chill. You won't get a response until ADB tries to connect to your Sensation. So go ahead and start ADB on your PC. Suggested command:
Code:
adb devices
"Now ADB started, but nothing's happening on my computer!!!"
Uh, didn't I just advise you to chill ? Take a look at your phone...
"What's this pop-up that just popped up??"
(See image below)
Congratulations, that is Android asking your permission to store an RSA key on your Sensation for ADB interaction with your PC.
Fearlessly accept it.
Hint: check the "Always allow from this computer" box to save time later on.
The RSA authentication key you just accepted will be stored on your phone in the file /data/misc/adb/adb_keys.
You are now good to go. Just 3 easy steps with a minimum of panic.
Questions? Problems? Ask away!
Many thanks to XDA member skipjacks for the idea for this post
Hi,
Nice! :good:
People should also not use USB 3.0 slots or USB hubs.
Try several slots if the front ones do not work.
Windows 7 & 8 drivers are HERE in case anyone needs them...
malybru said:
People should also not use USB 3.0 slots or USB hubs.
Click to expand...
Click to collapse
I understand about the hubs, but why not USB 3.0?
Skipjacks said:
I understand about the hubs, but why not USB 3.0?
Click to expand...
Click to collapse
Hi,
I have read a lot of instances of "Device not recognized" when using 3.0 slots.
I am not saying it will never work.
But ,if you use one,and it does not work,then,try it on a 2.0 slot.
Thanks for the post
few problems:
- I tried updating ADB with SDK manager. It kept saying something was accesing the installation folder. even after I closed explorer, virusscanner etc. I replaced the files with the zip attachement, but still a weird issue.
- another thing. Before I updated adb reported error: device offline. After update the issue persists. not using any hubs or USB 3.0. I think it's because I'm not using the stock cable that came with the phone.
onemanshow85 said:
Thanks for the post
few problems:
- I tried updating ADB with SDK manager. It kept saying something was accesing the installation folder. even after I closed explorer, virusscanner etc. I replaced the files with the zip attachement, but still a weird issue.
- another thing. Before I updated adb reported error: device offline. After update the issue persists. not using any hubs or USB 3.0. I think it's because I'm not using the stock cable that came with the phone.
Click to expand...
Click to collapse
Hi,
I think there is one solution that will address both issues. Before I mention it, let me ask: are you sure you enabled USB debugging on your Sensation? This is confirmed if, when you plug in the cable to your PC, you immediately get a USB debugging icon in the Notification Bar.
Glad we got that out of the way!
Unplug your device from the PC.
Anyhow, since you already have the SDK installed, the recommended way to update is to use the SDK Manager.
--in Windows, I think this is an executable in the tools sub-folder of your main android SDK folder. Double clock on it.
--in Linux, start up a terminal and type
Code:
android
if that doesn't do it, CD to the /tools directory in android-sdk-linux, or wherever you put the SDK, first. Then type "android".
The window that opens when you start SDK Manager should show that you need an update to (at least) platform-tools. Go ahead and do the update. You will have to accept some license(s) - accept it or them.
Once the install is complete, close SDK Manager.
Now plug your USB cable back in, and try out the "adb devices" command. It should work.
Suppose you still get "device not found", though. Try the following: again unplug.
Type the command:
Code:
adb kill-server
Now plug the phone back in, verify that you have USB debugging, and try "adb devices".
If no go, let me know what platform you are running, etc. I've heard it could be the cable, but I think that you just need to make sure it is plugged in securely.
BTW, the reason you probably won't have to do the adb kill-server step is that the SDK Manager kills running adb processes during the install.
Let me know how it goes!
Yrs,
dkephart
Sent from my HTC Sensation using xda premium
tnx. I was somewhat ehead of the steps you mentioned. problem was that SDK manager can't install anything cause it can't seem to kill any other adb proces. But I used a workaround for that so no problem there.
ADB does find my device, only it is stated as offline. I will have to try it again with the stock cable that came with the phone. Then I'll know if this is a software issue. Currently I'm using a complete random micro-USB cable wich I found on work laying around.
I'll let you know if stock cable is any difference. If so, it might be usefull info for ppl to know to always use stock cable while using ADB/Fastboot
onemanshow85 said:
tnx. I was somewhat ehead of the steps you mentioned. problem was that SDK manager can't install anything cause it can't seem to kill any other adb proces. But I used a workaround for that so no problem there.
ADB does find my device, only it is stated as offline. I will have to try it again with the stock cable that came with the phone. Then I'll know if this is a software issue. Currently I'm using a complete random micro-USB cable wich I found on work laying around.
I'll let you know if stock cable is any difference. If so, it might be usefull info for ppl to know to always use stock cable while using ADB/Fastboot
Click to expand...
Click to collapse
Yeah... my random selection doesn't have this problem. But I once seemed to have it with the official cable. You might want to try rebooting both the phone and the PC.
Sent from my HTC Sensation using xda premium
The stock cable did the trick. everything works fine with the stock cable.
So if ppl find any trouble using ADB with a cable other then stock, this might cause the problem.
onemanshow85 said:
The stock cable did the trick. everything works fine with the stock cable.
So if ppl find any trouble using ADB with a cable other then stock, this might cause the problem.
Click to expand...
Click to collapse
Great find...and extra points to anyone who determines why this might be the case...
Sent from my HTC Sensation using xda premium
dkephart said:
Great find...and extra points to anyone who determines why this might be the case...
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Some really cheap cables only have 2 wires in them and can only be used for charging. You need the other wires for data transfer.
But some companies only put the charging wires in to save money on the copper.
It must be a REALLY low quality cable though. I mean I get all my cables on Monoprice for like $1-$2 and they all work great for data.
Or, the cable does have all the internal wires and one is just broken inside.
Sent from my HTC Sensation using xda app-developers app
I've done everything in the thread, I can see my htc when I run the adb command but I don't get the pop-up on my phone. I tried the stock cable and different one but nothing. I'm on latest albinoman ROM. what should I do ?
P.S : I tried rebooting both the phone and pc but still the same problem.
nemovich said:
I've done everything in the thread, I can see my htc when I run the adb command but I don't get the pop-up on my phone. I tried the stock cable and different one but nothing. I'm on latest albinoman ROM. what should I do ?
P.S : I tried rebooting both the phone and pc but still the same problem.
Click to expand...
Click to collapse
You get your serial number and "device offline" from the adb devices command?
Sent from my HTC Sensation using xda premium
dkephart said:
You get your serial number and "device offline" from the adb devices command?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
no just the serial number
nemovich said:
no just the serial number
Click to expand...
Click to collapse
I'm puzzled, then. What happens when you do "adb shell"?
And if that comes back with the shell prompt (a $), then what happens if you type "su"?
Sent from my HTC Sensation using xda premium
dkephart said:
I'm puzzled, then. What happens when you do "adb shell"?
And if that comes back with the shell prompt (a $), then what happens if you type "su"?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
with adb shell I get $ and with su I get #.
nemovich said:
with adb shell I get $ and with su I get #.
Click to expand...
Click to collapse
Cool! Then you have adb working. To confirm, in the shell, "ls" should come back with a listing of the files on your device. If you do "cd sdcard" and "ls" you get the files on the SD card.
You're good to go.
Sent from my HTC Sensation using xda premium
Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
---------- Post added at 05:07 PM ---------- Previous post was at 04:57 PM ----------
Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
Sent from my HTC Sensation using xda premium
nemovich said:
Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
Click to expand...
Click to collapse
There is still a possibility adb did not update, or that you have more than one copy of adb on your system. Here's another way. cd to the android-sdk- windows folder (you are running windows, right?) and type
Code:
android update sdk --no-ui
...now the SDK manager will run. It takes a while. When done, reboot your PC and plug in your Sensation. Go to the platform-tools subfolder of your SDK folder and run adb from there. You could type "./adb" to make sure. Check your device - the homescreen has to be unlocked - and you should see the pop-up.
I don't really know about Android Commander, so there is always a possibility that that app doesn't handler things right, but I think this will work.
Let me know how it goes...
Sent from my HTC Sensation using xda premium
dkephart said:
There is still a possibility adb did not update, or that you have more than one copy of adb on your system. Here's another way. cd to the android-sdk- windows folder (you are running windows, right?) and type
Code:
android update sdk --no-ui
...now the SDK manager will run. It takes a while. When done, reboot your PC and plug in your Sensation. Go to the platform-tools subfolder of your SDK folder and run adb from there. You could type "./adb" to make sure. Check your device - the homescreen has to be unlocked - and you should see the pop-up.
I don't really know about Android Commander, so there is always a possibility that that app doesn't handler things right, but I think this will work.
Let me know how it goes...
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
when I cd to the sdk folder ( C:\Users\Documents\adt-bundle-windows-x86-20130219), it gives me command not recognized. I can run sdk manager from the folder and everything is up to date.
I run adb from platform-tools and it gives me the same thing as before.
one thing though, I don't see the "adbkey" file in platform-tools but it is there in ".android" folder. so I run it from the later folder too but the still the same thing, no pop-up.
it's not just android commander, a lot of other apps give the same thing.
Here is a way to install adb'fastboot on win8 or win8.1 for your htcm8 in less then 10 mins. only 1 Fully working m8 driver an 1 program needed to install an then your up an running adb/fastboot on win8.1 with nothing else to install no SDK no nothing
You simpley just launch program an start entrering adb an fastboot commands
DIRECTIONS
download the need files below
extract them [myself I did it to my desktop]
then to get driver to work always[no more waitng for device]
scroll to settings tab in bottom right screen
pick change pc settings an click update an recovery
next pick recovery
Then pick advanvced set up
REBOOT IS REQUIRED it should auto do this or prompt you do
then pick troubleshoot>Advance options>startup settings>click restart
once it reboots you need to disable driver signature enforcement by selecting number 7
Reboot once last time it will boot right to OS
Plug phone in>navigate to device manager I tested with a 2.0usb an stock cord
You should see your phone under other devices>click on it an select update driver software
pick find file yourself then navagte to file you extracted of driver>click ok an install driver.
Then simply install the minimal adb/fastboot program I would add desdktop icon
open program an type adb devices an yours will show up...[ if it shows offline check your phone for a prompt[it will be there if you get offline] check allow this pc an click ok
again type
adb devices an yours will show up an your good to go.
now you can reboot bootloader an try some fastboot commands
DOWNLOADS
download program from this thread
http://forum.xda-developers.com/showthread.php?p=53230508
driver
https://www.dropbox.com/s/toezcicvf9bm08v/drivers32_64bit.zip
CREDIT FOR MAKING THIS POSSIABLE
adb/fastboot program @shimp208
be sure to thank his thread for this
Reserved for later..
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Awesome can't wait to try them out
Sent from my HTC6500LVW using XDA Premium 4 mobile app
almania6 said:
Awesome can't wait to try them out
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It takes longer to read my OP then to actually do the process if you knew where to go already lol.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Link dead
Hello can you or anyone that still have that driver backup? Because the file no longer exist. Thanks
As you can see in title I want to record screen without root, I don't want to hook it up to PC and then start recording only for 3 minutes long. I want to do longer than that and without PC and the app be free. Does anyone know an app that can do that or I need to be rooted ?
Unfortunately if you don't want to use ADB to record you need root.
Yes you have hope!
Take a look at this thread: http://forum.xda-developers.com/showthread.php?t=2629723
I know it says you require adb but the command works perfectly even in the phone.
You'll need an app like Terminal Emulator to open up the console and type in the command.
No root required.
Sent from my XT1033 using XDA Premium 4 mobile app
KDB223 said:
Yes you have hope!
Take a look at this thread: http://forum.xda-developers.com/showthread.php?t=2629723
I know it says you require adb but the command works perfectly even in the phone.
You'll need an app like Terminal Emulator to open up the console and type in the command.
No root required.
Sent from my XT1033 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK cool thanks for thread, so I just have to put those commands into android terminal on phone and it will work ?
This is what I get when doing the commands
bublz654 said:
This is what I get when doing the commands
Click to expand...
Click to collapse
Noooooooooooo... That's not what you do.
'adb' is for your PC ONLY.
Type whatever is there after 'adb shell'
For example, type 'screenrecord /sdcard/video.mp4'
See, the adb shell command on your PC allows you to control your Android's terminal FROM the PC.
Instead, you can simply type the commands after 'adb shell' into your Android's terminal.
Sent from my XT1033 using XDA Premium 4 mobile app
KDB223 said:
Noooooooooooo... That's not what you do.
'adb' is for your PC ONLY.
Type whatever is there after 'adb shell'
For example, type 'screenrecord /sdcard/video.mp4'
See, the adb shell command on your PC allows you to control your Android's terminal FROM the PC.
Instead, you can simply type the commands after 'adb shell' into your Android's terminal.
Sent from my XT1033 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh right OK. So I can do anything that has adb shell after it ? But I don't see adb shell in that tutorial
Oh never mind . that means I need to be hooked up to PC to record all the time. I don't want to be beside PC all the time trying to record
bublz654 said:
Oh never mind . that means I need to be hooked up to PC to record all the time. I don't want to be beside PC all the time trying to record
Click to expand...
Click to collapse
No!
You don't seem to get my point.
Try this :
Open terminal, type the following -
screenrecord --time-limit 10 /sdcard/demo.mp4
This should record a 10 second long session from your screen and dump it into a video.
Sent from my XT1033 using XDA Premium 4 mobile app
KDB223 said:
No!
You don't seem to get my point.
Try this :
Open terminal, type the following -
screenrecord --time-limit 10 /sdcard/demo.mp4
This should record a 10 second long session from your screen and dump it into a video.
Sent from my XT1033 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
10 sec long video. I'll be here forever trying to record games
bublz654 said:
10 sec long video. I'll be here forever trying to record games
Click to expand...
Click to collapse
I don't know the maximum allowed time, but if you don't type the '--time-limit' flag, its set to 3 mins by default.
Guess its impossible to record games if max time is limited to 3 mins. You got no choice other than rooting then.
Sent from my XT1033 using XDA Premium 4 mobile app
KDB223 said:
I don't know the maximum allowed time, but if you don't type the '--time-limit' flag, its set to 3 mins by default.
Guess its impossible to record games if max time is limited to 3 mins. You got no choice other than rooting then.
Sent from my XT1033 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol, when I do the command it saves a file but it says cannot play file. And the file is 0.00kb. I don't want to root now because of android L near. But thanks for help though