Database Info

[HOW-TO] ADB for Dummies(How-To Learner's Guide)

Hi,
My name is Joe aka AndroidSamurai.. I will be releasing more guides and media content in the weeks to come.
I'm currently very busy with "life events(new baby)" and apologize for my absence.
I will be updating this post since it was my original with a new guide updated to new SDK and Android methods.
Thanks again,
AndroidSamurai
Android4D Inc

<golf clap>
Well done.
</golf clap>

What do i do if the new hardware device notification doesnt pop-up ? NM i got it. Thanks for the writeup

@King_tee: Assuming windows, you follow the following steps.
1. Start > Control Panel > System.
2. Hardware > Device Manager
3. Click on the last icon below the File menu. It should correspond to "Scan for Hardware Changes."
If that doesn't work, try unplugging / replugging USB cable, different USB cable, restarting phone, restarting computer, etc.

If you never see the notification, navigate to the Device Manager(inside "System" in the control panel in XP and inside Device Manager on Vista).
You will see ADB Android Device at the top of the list with a Yellow Icon beside it meaning the device is not working. Right-click on the device and select "Update Driver".
Follow the dialogs that pop-up and navigate to where the unzipped drivers are at...
You should be good to go from there...

ok, i need some help please... I downloaded the SDK and followed the instruction in this thread, but when i try to update my driver for the phone, it says the driver is not compatible with my phone.. I am using Haykuro's ROM 4.5 with FW 1.5.. would that be the reason for this issue?

devildogg2001 said:
ok, i need some help please... I downloaded the SDK and followed the instruction in this thread, but when i try to update my driver for the phone, it says the driver is not compatible with my phone.. I am using Haykuro's ROM 4.5 with FW 1.5.. would that be the reason for this issue?
Click to expand...
Click to collapse
you may need to uninstall the current driver for your phone if you have mounted it before downloading the SDK. if you don't have the SDK setup the first time you plug the phone in then your computer will auto-update the driver to a regular UMS driver and it won't help you when you try adb. i forget how to uninstall your current driver since i don't use windows, but i'm sure you can find a nice crash course online

tubaking182 said:
you may need to uninstall the current driver for your phone if you have mounted it before downloading the SDK. if you don't have the SDK setup the first time you plug the phone in then your computer will auto-update the driver to a regular UMS driver and it won't help you when you try adb. i forget how to uninstall your current driver since i don't use windows, but i'm sure you can find a nice crash course online
Click to expand...
Click to collapse
I dont know if thats the problem because when i plug it in, it doesnt show up as a notification, and when i go to the device manager it shows the little yellow triangle.. I'll look again. Thanks for the quick reply though. I am no expert in linux, but i have it installed, let me see if i can figure it out there..

tubaking182 said:
you may need to uninstall the current driver for your phone if you have mounted it before downloading the SDK. if you don't have the SDK setup the first time you plug the phone in then your computer will auto-update the driver to a regular UMS driver and it won't help you when you try adb. i forget how to uninstall your current driver since i don't use windows, but i'm sure you can find a nice crash course online
Click to expand...
Click to collapse
ok, so i am in linux now, and i just noticed this guide was for windows.. lol can you or someone tell me how to install the SDK on linux?

devildogg2001 said:
ok, so i am in linux now, and i just noticed this guide was for windows.. lol can you or someone tell me how to install the SDK on linux?
Click to expand...
Click to collapse
Downloading
http://developer.android.com/sdk/1.1_r1/index.html
Installing
http://developer.android.com/sdk/1.1_r1/installing.html
Found through Google...imagine that.

as well as what xyrcncp said can you you can download it and just mv ~/Desktop/sdk/tools/adb /usr/bin/adb abd you should be able to run the adb commands from any directory. not too hard to cd to the correct directory but i personally don't like to type cd ~/Phone/tools/android-sdk/tools every time cause i tend to make typographical errors. let me know how it worked but you shouldn't have any problems at all

umm no offense but your writing a tutorial for people that are not sure on how to do this, so you must assume that they do not know how to run an executable file...... write yourself a better tutorial without actually bashing the self esteem of some people... tutorials are positive not negative. I already know all of this but still... dont degrade someone due to the fact they dont know how, thats the whole point of writing your tutorial. Nothing should have been left out (including how to run a .exe .com or .bat
" (If you do not know how to install a windows executable file, please kill yourself now! ) "
this isnt honestly written with any hatred towards you, it was a good tutorial. Just might want to think about how you write it next time.

The "bashing" comments in my tutorial are directed towards the people with a true sense of humor. My tutorial was written to tell you how to simply complete a task and not to make you feel better about yourself. I do not get pleasure in abusing people's self esteem nor do I enjoy putting people down.
Just because you got a little sand in your crack does not mean you need to come in a very honest and informative thread and start bashing the people who are bending over backwards to help everyone out.
The reason I created this "tutorial" in the first place was because all the other threads are full of "start searching and stop asking so many damn questions" comments.
So start looking in the mirror when you wake up in the morning and stop saying "My, I think I will run over to good ole' XDA and be an @$$ to everyone today".
I am sincerely sorry that a little sense of humor has caused so much hatred in my thread. Please contact the forum moderators and see if the think my tutorial is so hateful.

lol i dont see any hatred but anyway when i download the adb driver when extracting it says unknown method

@ Nabzilla1990
Are you using Windows or Linux?
Are you using the built-in Zip tool or 7-zip from the links I provided?
Are you using a 32 or 64-bit OS?

using the same operating system as you 64bit vista ultimate sp1 and using winrar to extract

Try using 7-zip man, I have been using it for 3 yrs now.
Basically what I am saying is that everything in my guide is guaranteed to work.

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.

it worked with 7-zip thank you and also want to add if it doesnt work for some people plug in ur phone and update the usb mass storage with the usb driver from here and it should work i had that problem earlier

Okay, so I did everything and got up to run cmd, when I type in the cd C:\android-sdk-windows-1.1_r1\tools it says not a specififed folder, but when I type it without the \tools it doesnt work. can anyone help?

Froyo Root Instructions using Superoneclick And Unrooting

ROOTING:
Since z4root, one of the easiest ways to root, is not working on Froyo in Galaxy 3, I decided to make this separate thread for instructions on how to root Froyo using Superoneclick.
First and foremost: Enable USB Debugging by going to Settings>Applications>Development. Make sure it is ticked.
Download the attached Superoneclickv1.5.zip file. Extract its contents. Make sure your phone drivers are installed on the computer (Samsung Kies). Then follow the steps:
1. From the extracted contents, run the file named Superoneclick.
2. Turn off your phone, then connect it to the computer using the USB Cable. Don't turn on the phone. Keep it off but connected to the computer.
3. In Superoneclick, click on the 'Root' button. After a few seconds, it'll say 'Waiting for device'.
4. Now turn on your phone (while it is still connected to the computer). Superoneclick will detect the phone.
5. Now the phone will be rooted, while it is starting up. When it is started, it'll be rooted.
6. After rooting, download and install busybox on your phone. It should take care of any slowing down of your phone after rooting.
That's it. The phone is now rooted, although it would be so much better if z4root worked on Froyo..
For those getting stuck at the 'pushing raceagainstthecage' step, try this method. Credits go to haree:
1. login as admin and then open the application. Or right click on Superoneclick.exe and click on 'Run as administrator'.
2. turn off ur Virus protection
3. remove all the additional external USB devices(this seems to confuse the SW)
i removed all the above mentioned
and then follow the instructions u will be successful
it worked for me now i have 2.2 and rooted
Click to expand...
Click to collapse
UNROOTING INSTRUCTIONS:
Unfortunately, the method to unroot by clicking on the Unroot button in Superoneclick does not work. So follow the following steps to unroot.
1. Download rootexplorer.apk (attached) and install Root Explorer on phone.
2. Run Root Explorer. A 'Superuser Request' prompt will come up. Press Allow.
3. Now, on the top, there will be a button saying 'Mount R/W'. Press it. It should change to 'Mount R/O'. The button should say 'Mount R/O' in order for you to be able to do anything in the following steps.
4. Now scroll to the bottom, click on system. Then click on bin.
5. In the bin folder, look for a file named 'su'. Long press on this file, and select Delete to delete it.
6. Now go back to the system folder by pressing the Back button once.
7. Now enter the app folder. Scroll down and look for the file named 'superuser.apk'. Long press on this file and delete it.
8. Exit Root Explorer after this. Uninstall it if you don't want to use it.
9. That's it. Your phone will be un-rooted.
Another method to unroot:
1. Download and install Terminal Emulator (attached).
2. Run Terminal Emulator on the phone. If you don't see a keyboard to type, press Menu and press Toggle Soft Keyboard.
3. Type su and press enter. Press Allow on the 'Superuser Request' prompt. The $ sign will change to a #.
4. Now type the following line exactly as it is and press enter: mount -o rw,remount /dev/block/mtdblock3 /system
5. Nothing will happen visually. The pointer will shift to a new line.
6. Now type the following line and press enter: rm /system/bin/su
7. Again, type following line and press enter: rm /system/app/superuser.apk.
8. Now exit Terminal Emulator. Your phone is un-rooted.

Hehe, first i thought it makes no sense to write a howto on this since its described in the SOC thread anyway, but man the idea to do it during boot is ubercool, didn't think of that...

FadeFx said:
Hehe, first i thought it makes no sense to write a howto on this since its described in the SOC thread anyway, but man the idea to do it during boot is ubercool, didn't think of that...
Click to expand...
Click to collapse
I know it's explained in the SOC thread, but many people keep asking on the "Samsung Galaxy 3 GT-i5800: root, gps fix, upgrading" thread about rooting Froyo, so I thought it's better to have one SOC thread right in the Galaxy 3's Development Section. It'll save everyone reading through a lot of pages on that thread..

addicted2088 said:
I know it's explained in the SOC thread, but many people keep asking on the "Samsung Galaxy 3 GT-i5800: root, gps fix, upgrading" thread about rooting Froyo, so I thought it's better to have one SOC thread right in the Galaxy 3's Development Section. It'll save everyone reading through a lot of pages on that thread..
Click to expand...
Click to collapse
hi
when i see a few reports that this is working for our G3 ill add this link to the roll up thread very nice of you to give this info to all keep up the good work
one question will this also un root the phone

haree said:
hi
when i see a few reports that this is working for our G3 ill add this link to the roll up thread very nice of you to give this info to all keep up the good work
one question will this also un root the phone
Click to expand...
Click to collapse
Can't unroot using the same procedure, but have added another procedure to do it.
This method does work for everyone. The only new step in my procedure is to do it while the phone is booting.

help! !
cant root. stuck at "waiting for device"..... tried everything.. no luck. can anyone help?

coolzarjun said:
cant root. stuck at "waiting for device"..... tried everything.. no luck. can anyone help?
Click to expand...
Click to collapse
Are your phone drivers properly installed? Does your computer make a 'Hardware connected' ding sound when you turn on the phone? If not, then you'll have to install Samsung Kies and then connect the phone to the computer to install the drivers. Try rooting after that.

all drivers are installed.. i reinstalled twice.. when i connect in usb debugg.. says installing some adb stuff after fews secs.. comp says hardware might not work properly not properly installed. all other drivers wrk fine.. wat can i do to install adb drivers properly. . i have windows xp

coolzarjun said:
all drivers are installed.. i reinstalled twice.. when i connect in usb debugg.. says installing some adb stuff after fews secs.. comp says hardware might not work properly not properly installed. all other drivers wrk fine.. wat can i do to install adb drivers properly. . i have windows xp
Click to expand...
Click to collapse
Connect your phone to your computer. Then open the Device Manager. Then look for the entry 'SAMSUNG Android Composite ADB Interface' in the list. It might be under the ADB Interface tab. Right click on the 'SAMSUNG Android Composite ADB Interface' and uninstall it.
Then reconnect your phone to the computer and see if the ADB drivers get installed properly this time.

did that also....uninstalled and connected the phone. still the same error..
hardware not properly installed.. it might not work properly
i got windows xp 32-bit
can u help ?? plz !

coolzarjun said:
did that also....uninstalled and connected the phone. still the same error..
hardware not properly installed.. it might not work properly
i got windows xp 32-bit
can u help ?? plz !
Click to expand...
Click to collapse
Sorry, I'm using Windows 7, so I've no idea what to do about the drivers in Windows XP. Try updating Kies..

i also have win 7 and it doesnt work...help??

reist said:
i also have win 7 and it doesnt work...help??
Click to expand...
Click to collapse
I can't help if the drivers on your computer are not installed properly. After connecting the phone while it is ON, open the Device Manager and see if the ADB driver is properly installed.
If the drivers are properly installed, this method will work..
Edit: As mentioned by mhndk14 below, enable USB Debugging in Settings>Applications>Development.

I also had the same problem with windows 7. Just make sure that the USB Debugging is enabled and then try again. It worked for me.

how to bring the phone back to factory settings
hi how can i get back my phone to the original factory settings? i rooted using z4mod and when unrooted the live wallpapers wont go... and how do i get my boot menu when restarted on my 1 5801??

nageshkaja said:
hi how can i get back my phone to the original factory settings? i rooted using z4mod and when unrooted the live wallpapers wont go... and how do i get my boot menu when restarted on my 1 5801??
Click to expand...
Click to collapse
To remove the Live Wallpapers, you'll have to root your phone, and then use Root Explorer to remove the files Livewallpaperspicker.apk from system/app, and libRS.so and librs_jni.so from system/bin. Then un-root your phone. Be sure to press the 'Mount R/W' button in Root Explorer to be able to delete the files.
As for restoring your boot menu, that procedure is there somewhere in the Development section. The boot menu changes because of upgrading, not rooting.

It seems i have lost haptic feedback after rooting(jpb), anybody else experience this?
Edit: lol
It was probably sue to the "forced" reboot, but I accidently dropped my phone (batteries feel out) and now it's working

stubborn_d0nkey said:
It seems i have lost haptic feedback after rooting(jpb), anybody else experience this?
Edit: lol
It was probably sue to the "forced" reboot, but I accidently dropped my phone (batteries feel out) and now it's working
Click to expand...
Click to collapse
Yeah, haptic feedback stops working sometimes on JPA and JPB after rooting. But restarting the phone corrects it. (Although your method of restarting the phone was too brutal!! )

Thanks addicted2088...worked perfectly...

successfully rooted..........
now i need to know how to install live wallpapers......
thanks

[Q] rooting inspire questions

Hello everyone I'm in the dinc2 forums. I'm a marine and the other day I was showing a guy I work with my s-off rooted dinc2 running miui and he immediately was interested. He has the inspire and I was looking for a little know-how on what to do and we don't really have the time to search religiously due to work. He's running stock 2.3.3 any help would be appreciated if you want to email me my email is [email protected]
Thanks!

Linch89 said:
Hello everyone I'm in the dinc2 forums. I'm a marine and the other day I was showing a guy I work with my s-off rooted dinc2 running miui and he immediately was interested. He has the inspire and I was looking for a little know-how on what to do and we don't really have the time to search religiously due to work. He's running stock 2.3.3 any help would be appreciated if you want to email me my email is [email protected]
Thanks!
Click to expand...
Click to collapse
Ace Hack Kit
That will walk you through the root/s-off/unlock process. It's been VERY much simplified over time, now it's just a 1 step process. Read the effen manual a few times before you start - but like I said, at this point it's very straight-forward.
Once installed hit up the MIUI thread. Basically you'll download the ROM to your SD, boot to recovery, perform a wipe, and flash the ROM
And thank you for your service and dedication to this wonderful country of ours!

He said the adb drivers won't connect

Any specific error messages? At what point is this happening? Is he trying to run the hack kit or just trying to access an ADB shell?
The hack kit contains all necessary adb files/drivers
Make sure he's done all of this:
Make sure HTC USB Drivers for Android are installed (included in the Hack Kit @ tools/windrivers)
Disable all malware detection, including Windows Defender
Uninstall HTC Sync
Uninstall Droid Explorer
Uninstall iTunes or stop service
Uninstall Other phone pda or tablet software

We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?

trouble rooting my phone
when i run the hack as admin on windows 7 it give an error message this is what the error message says
check adb connectivity
shad0fox04/2011
service not running
error error error
phone not plug in or driver not installed or usb debugging not enable
error error error
pres any key to continue the it just cut off i checked all of that and everything is good to go so what is the problem lol

did u ever find out y adb wont connect im having d same problem

Linch89 said:
We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?
Click to expand...
Click to collapse
Did you install the drivers that came with the kit just to be safe?? I just did this like 2 days ago and it worked perfect..

Linch89 said:
We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?
Click to expand...
Click to collapse
Has he by any chance tried a different USB port? And is the phone in charge only mode, it's not mounting itself as a disk drive automatically? I don't know how feasible it might be, but if he has another computer available try running it there and see if you get any different results. At least then we might be able to narrow down better whether it's the software, the computer, or the phone.
jonathanj942 said:
when i run the hack as admin on windows 7 it give an error message this is what the error message says
check adb connectivity
shad0fox04/2011
service not running
error error error
phone not plug in or driver not installed or usb debugging not enable
error error error
pres any key to continue the it just cut off i checked all of that and everything is good to go so what is the problem lol
Click to expand...
Click to collapse
Another simple thing that I have to ask about...you guys did extract all the contents of the hack kit somewhere on your computer, correct? You're not trying to run it from the .zip?
If it is extracted,
go to the tools\win\ directory.
Hold Shift and Right-Click in an empty spot, select "open command window here"
type "adb devices" and hit Enter
You should see 12 alpha-numerics listed under "List of devices attached"
If you don't see anything under this, then for some reason adb isn't recognizing your phone is plugged in. In which case I'd try a different USB port or computer

Does anyone know how to root from 2.11.605.9 on a Mac? Auto or manual?

I've never done manual before.... so I'm completely illiterate here...

Easiest way is downgrade to 2.11.605.5 and then use the revolutionary tool
Sent from my ADR6400L using XDA App

carycooke said:
Easiest way is downgrade to 2.11.605.5 and then use the revolutionary tool
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
That tool works on Mac??? Also, not sure how to downgrade on a Mac either...

Go here http://forum.xda-developers.com/showthread.php?t=1401959
Download 2.11.605.5 file
Rename it to what it needs to be then boot to hboot downgrade
Then run the revolutionary tool
Find it on your mac on the web
If its not compatible I suggest running a emulator or downgrade and then get on a windows computer to run tool for a second
Sent from my ADR6400L using XDA App

crispy8826 said:
That tool works on Mac??? Also, not sure how to downgrade on a Mac either...
Click to expand...
Click to collapse
Downgrading has nothing to do with the computer, it's all with the phone.
As far as rooting the Thunderbolt on a Mac is concerned, you're better off just going to a Windows computer. I tried to do it on a Mac first but after around 8 hours of getting nowhere, I just used a friend's PC. If you're still trying to root and are having problems or if you can't downgrade the radio, let me know and I'll help.

ThunderNet said:
Downgrading has nothing to do with the computer, it's all with the phone.
As far as rooting the Thunderbolt on a Mac is concerned, you're better off just going to a Windows computer. I tried to do it on a Mac first but after around 8 hours of getting nowhere, I just used a friend's PC. If you're still trying to root and are having problems or if you can't downgrade the radio, let me know and I'll help.
Click to expand...
Click to collapse
I was able to root from a Windows 7 VM running in Fusion.
BTW, you don't have to downgrade to use Revolutionary to root. Here's a workaround: http://androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html

dittman said:
I was able to root from a Windows 7 VM running in Fusion.
BTW, you don't have to downgrade to use Revolutionary to root. Here's a workaround: http://androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
Click to expand...
Click to collapse
Honestly, I found that just downgrading the radio was easier, but I'm not very good at using adb so that's probably why.

crispy8826 said:
I've never done manual before.... so I'm completely illiterate here...
Click to expand...
Click to collapse
I just did it this morning but on Windows 7, I did it with the same firmware that you have also, I posted up my experience in doing so right on the forums here, in the Thunderbolt Section > General (I cant post links yet lol)
Maybe it will be helpful! But as far as I know revolutionary (Which it uses) Is Windows/Linux only, try a VM!

No loss method posted on YouTube
I just went through a procedure posted on Youtube by Nat3Mil that starts with a temp root of the 605.9 that then allows you to use revolutionary to root without data loss. I am running my first titanium backup on my now rooted thunderbolt 605.9 now and I am at the green end of noob town.
Since I cant paste links you will have to try a search for temp root 605.9 might throw Nat3Mil in for good measure.
here is the written part of the guide with the links removed
//WRITTEN GUIDE
1. install htc drivers
2. plug thunderbolt into computer
3. turn on usb debugging (settings, applications, development, (check) usb debugging, okay
4. download ThunderboltTempRoot.zip from link below
5. extract package to C:\
6. click start, type cmd, press enter
7. in command promt type
cd c:\ThunderboltTempRoot (press enter)
adb devices (press enter)
(at this point you should see your device listed with serial #, if not, reinstall the driver, make sure usb debugging is on, and remove any syncing software from computer (htc sync, itunes, etc) then try again. you cant continue unless your device is listed!)
adb push fre3vo /data/local/tmp (press enter)
adb shell chmod 777 /data/local/tmp/fre3vo (press enter)
adb shell /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF (press enter)
8. Your thunderbolt is now temp rooted. DO NOT REBOOT or youll have to do this over.
9. go to my rooting video linked below and follow along to get perm root without wiping data! (you can skip the driver install, its the same driver as above)
Also on the video that he did showing the revolutionary part there was this note that speaks more to the original post:
SUCCESS! Booya, you rock. I used your other video for getting S-OFF with Gingerbread 2.4.3 and software update 2.11.605.9. Everything worked as shown in the videos. To my Apple-brandishing cohorts: I was able to do this with Windows XP via Parallels on a Macbook Pro. Make sure to have Parallels attach the phone to the Virtual Machine. Also, you might want to download the files required using a Windows browser just to prevent and corruptions issues when transferring between OSes.

Getting ADB access in Android 4.2.2

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.