Database Info

[Q] adb error using shift root and recovery

Help! When I try to root my evo shift with gui shift root and recovery all I get is an adb error message. I have installed htc sync on my laptop. I also cannot connect to sync. These problems may be related? I am running windows vista.

sounds like the drivers may not have installed... Where did you get the version of sync you installed? You're best bet is to use the one off the sdcard. I've had an occasion or two also where things got messed up, and I uninstalled it all and reinstalled. (under programs and features you'll find HTC sync and driver installer, remove both and reinstall if necessary)

I installed it off the sd card and have did the install/ uninstall at least 5 times. still no luck.

i had same error but i just did mine maually. theres a video now for manually rotting it. if you fllow the steps you will root your shift

candler72 said:
I installed it off the sd card and have did the install/ uninstall at least 5 times. still no luck.
Click to expand...
Click to collapse
I'm in the same boat no matter what I do it my shift won't connect to sync and when I run adb devices it kicks a blank line then right back to platform-tools I'm running Vista myself and messed with it for hours and no luck I'm mad because I have rooted my shifts already and don't know what went wrong with the drivers sync or my pc this sucks as I need to be able to adb to help test some things
Sent from my PG06100 using Tapatalk

You do have adb debugging on right... the only other thing I could think of.

Yes I do have debugging on.

have you tried getting sync from htc's website to be sure?

If I'm correct the old version of syn from sprints website was giving me problems loading the drivers. I used the newest version from htc website and voila I was good to go. U may want to try that. I just re rooted earlier use the gui and it worked like a charm
Sent from my PG06100 using Tapatalk

I have the sync from htc website. I still get error running adb try again. Ive used the same usb cord and ports with my archos pad and have no trouble transfering files.

What exactly does the error message say? And with what command?
Sent from my PG06100 using XDA App

Error running and. Try again
Sent from my PG06100 using XDA App

Adb
Sent from my PG06100 using XDA App

Maybe it's your sdk that is messed up... Maybe try downloading and installing again.
Sent from my PG06100 using XDA App

Ive got temp root now with visionary. And have it set to reroot when i turn my phone off/on. I have wireless tether (non adhoc) which is what I was wanting to tether my archos 101. I still can't connect to sync. Wondering if its a vistas issue?

danaff37 said:
What exactly does the error message say? And with what command?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
I dunno what the other guys error is but I know on mine if I go to device manager there is an error code 37 with my HTC on my Vista pc.....I can cd to my c:\Android\Android-sdk\platform-tools
But when I hit add devices it kicks back and empty line after it starts the Damon on whatever then right back out to platform tools...it does the same thing with every sync I install, plus my phone can't find sync on my pc at all even if its open...and help would be really appreciated
Sent from my PG06100 using Tapatalk

candler72 said:
I have the sync from htc website. I still get error running adb try again. Ive used the same usb cord and ports with my archos pad and have no trouble transfering files.
Click to expand...
Click to collapse
I'm having the "error running adb try again" problem as well. Unfortunately when I try to run adb from the cmd prompt its output goes to a popup cmd prompt window which disappears before I can read it. My guess however is that it's blank like yours.
I'm convinced I've done everything they way I'm supposed to. Has anyone yet gotten the htc drivers to work under vista?

I had this same issue with ADB..all I did was, while connected via usb, uncheck debugging and then recheck. Clicked root again and it worked.

Sigh, there was a adb update. Install the new version from the sdk, delete the one in shiftrr, copy the new one in, close adb with task manager, then run as you were trying to do before. That fixed it for me.
And make sure when you install the recovery, not to use the one it comes with, it doesn't support the newer roms we have on the shift now. If you want to flash current ones, use clockwork 5.0.2.0, our twrp (recommended)

[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

[Q] Obtaining root on generic tablet

Ok I've got a generic tablet from Walmart, the DOPO MD-740. It's running ICS 4.0.3. I've been in contact with customer service about this thing, and while they're friendly and courteous, they really don't know anything about their product. According to their lead tech "there is no recovery or download mode".
Headache.
Well fooling around with this device, I've found.... SOMETHING....
While holding the volume up button at the same time as the power button, it boots straight to one single image, shown below. I have a feeling it's the download mode. Whatever it is, it's progress. Can anyone recognize what I got into? It's not a fatal error-- when I hit the reset button and reboot the tablet normally, all is fine.
I've tried to reboot into recovery via adb but I get the message that the command is not allowed. And of course, su is not allowed either.
Anyone have any suggestions on running adb on my computer... what process I would need to follow to manually root an ICS tablet? Would I just follow the same steps as I would in manually rooting a gingerbread device, or is there different lines of code I would need to use for ICS?
As for what device the kernel for THIS device has been ported from (it's obviously emulating something that has a magnometer which this unit doesn't have, etc...)... tech support doesn't know that either. The only clue I have that MIGHT help (other than the kernel version, build number, etc... all this is documented in another post, if anyone cares to take a look) is the FIRST boot image is of the penguin.
I would appreciate ANY feedback/information/advice anyone could offer in progressing with this "adventure"!
Thanks
Well with another twenty minutes of blindly pressing buttons I've found the recovery mode. From the screen displaying the android with the open panel (which I have concluded is NOT the download mode), pressing volume up, back, and power at the same time opens the recovery mode. The recovery is:
Android system recovery <3e>
Recovery system v4.00
No option to apply zip from sd, I guess this is to be expected on a stock device.

hi
in application select usb debug mode
install from unknown sources
connect to pc and run DooMLoRD_v4_ROOT
should work
regards
fred

didn't work.
After adb started successfully, sat for two hours and did nothing.

hi
are you using windows ?
is it reconized by windows ? do you have the drivers installed ?
ich processor use that tablet ?

Yeah I'm running Windows Vista, and my PC does recognize the device when it's connected (says drivers have been installed properly when connected under USB debugging mode, no problem transferring files in USB mode)
It's the ARMv7 processor
The device is recognized as Full ASOP on Rk29sdk

I've run across a new problem, which might actually be the main issue of the WHOLE problem. I was trying to push some files with adb from my laptop and it came to my attention that the driver for my device only acknowledges it as a mass storage device, even when the tablet is NOT mounted for mass storage. SOOOO... I guess I need a driver that will allow me to use adb. Any suggestions?

did you try with the drivers package from sdk ?

yup. Even gone as far as uninstalling the adb and sdk programs I had on my pc, downloading the newest versions and reinstalling. My computer "recognizes" the divice, but only as folders. Even when it's not mounted as mass storage.

STILL having te driver issue. Anyone have any suggestions on how to fnd a driver that will work with adb?
Sent from my Full AOSP on Rk29sdk using XDA

How did I root my “Full AOSP Rk29sdk”-MID 7-inch tablet (Android 4.0.3)
Hi Wingnut79 and others,
I have an Android 4.0.3 Tablet 7 inch, named "Full AOSP Rk29sdk" - and was also eager to root it....
After hours of search, trial and error, I succeeded.
My tablet is now fully rooted, and I can use ROM manager and all the aps for rooted android-devices....
How did I do that ?
I explain it here, in the attachment...
As you can see, my Windows is in the Dutch language, so I nevertheless hope everyone can understand what to do where...
I hope this can help...

Make sure it's not a Chinese Apad!
Make sure it's not a Chinese Apad! If u go on ebay u will see tons of tablets with ics 4.0.3. but the android on it it's a modified and weird version. I doublt it even is ics. One of my friends have it, and he cannot use the App Market, bcuz it said "Device not compatible with Market". Did u successfully downloaded stuff form the Market? If not, that maybe it's a piece of Chinese crap and u should call walmart for a refund.

It downloads apps from Android Market, Getjar, Amazon etc... just fine.
BAUDI--
I will try this later this afternoon, is it going to be an issue that my laptop OS is windows vista?

Mine tablet is a chinese tablet - but it's clearly really Android 4.0.3.
So, I also download and install applications from Playstore /Android Market/ etc.
It has Wifi, Bluetooth, 3G, GPS-AGPS, FM-radio,.... and evrything works really fine.
My sole problem was: no rootaccess (what I didn't understand, because it's "Android Open Source Project"...?)
Wingnut79,
as far as described in the guide I refer to, it works equally well on Vista. Just sometimes a little bit other name or place to find the properties or so - but should not be a problem at all.
I forgot to insist on the need to kill and restart adb after each change. I am not sure its really necessary each time, but I experencied that when I first thought "again nothing", it seemed well to work after "adb kill-server" and then "adb start-server"....
At some steps (I can't remember wich) I even rebooted my PC....
Now, everything works immediately...
So ROM Manager etc. works well, I have SuperUser... etc .
Good luck!

baudi said:
Mine tablet is a chinese tablet - but it's clearly really Android 4.0.3.
So, I also download and install applications from Playstore /Android Market/ etc.
It has Wifi, Bluetooth, 3G, GPS-AGPS, FM-radio,.... and evrything works really fine.
My sole problem was: no rootaccess (what I didn't understand, because it's "Android Open Source Project"...?)
Wingnut79,
as far as described in the guide I refer to, it works equally well on Vista. Just sometimes a little bit other name or place to find the properties or so - but should not be a problem at all.
I forgot to insist on the need to kill and restart adb after each change. I am not sure its really necessary each time, but I experencied that when I first thought "again nothing", it seemed well to work after "adb kill-server" and then "adb start-server"....
At some steps (I can't remember wich) I even rebooted my PC....
Now, everything works immediately...
So ROM Manager etc. works well, I have SuperUser... etc .
Good luck!
Click to expand...
Click to collapse
Just because it says it is 4.0.3 doesn't mean its pure AOSP. Remember that the China gov has its hands into a lot and there are things that they like to install on their devices to monitor the users and then close it up so it can't be changed.
Sent from my Inspire 4G using Tapatalk 2

this app rooted my Full AOSP on rk29sdk
I tryed many ways trying to root my tablet, even unlockroot.exe
I found SuperOneClickv2.3.3 and it found my tablet right off, it said my tablet looks rooted( but I knew it was not) so I let it do the root process, it installed superuser also
SuperOneClickv2.3.3
you may have to temp turn your virus program off, I use avira so I right clicked the task bar icon and unchecked realtime protection

universel root
try the universel root for the version of android you have or of similar tabs

asdera-and said:
try the universel root for the version of android you have or of similar tabs
Click to expand...
Click to collapse
Where can we find this?
Is there a download link?
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
carl1961 said:
I tryed many ways trying to root my tablet, even unlockroot.exe
I found SuperOneClickv2.3.3 and it found my tablet right off, it said my tablet looks rooted( but I knew it was not) so I let it do the root process, it installed superuser also
SuperOneClickv2.3.3
you may have to temp turn your virus program off, I use avira so I right clicked the task bar icon and unchecked realtime protection
Click to expand...
Click to collapse
Hello,
So SuperOneClick did work for you?
What kind of tablet do you have?
What version of Android was it running when you used SuperOneClick?
Thank you,

baudi said:
Hi Wingnut79 and others,
I have an Android 4.0.3 Tablet 7 inch, named "Full AOSP Rk29sdk" - and was also eager to root it....
After hours of search, trial and error, I succeeded.
My tablet is now fully rooted, and I can use ROM manager and all the aps for rooted android-devices....
How did I do that ?
I explain it here, in the attachment...
As you can see, my Windows is in the Dutch language, so I nevertheless hope everyone can understand what to do where...
I hope this can help...
Click to expand...
Click to collapse
I tried this and it worked. I got root on my device thanks alot for the guide.
Now to the real problem. I have two identical devices (rk29sdk). One is not booting and I can't manage to reset it.
My idea is make a full backup of the working device and somehow install it on the other one (the broken).
How can I do that - when I try to connect with adb it says:
Code:
C:\Windows\system32>adb devices
List of devices attached
0123456789ABCDEF device
Then this
Code:
C:\Windows\system32>
C:\Windows\system32>adb backup -apk -shared -all -f /backup/mybackup.ab
adb: unable to connect for backup
So it sees the device but I can't backup?
[edit]Now I connect to the device, the 'adb reboot' command works and the device responds. it's just the backup command that is not working.
Please help

asemore said:
I tried this and it worked. I got root on my device thanks alot for the guide.
Now to the real problem. I have two identical devices (rk29sdk). One is not booting and I can't manage to reset it.
My idea is make a full backup of the working device and somehow install it on the other one (the broken).
How can I do that - when I try to connect with adb it says:
Code:
C:\Windows\system32>adb devices
List of devices attached
0123456789ABCDEF device
Then this
Code:
C:\Windows\system32>
C:\Windows\system32>adb backup -apk -shared -all -f /backup/mybackup.ab
adb: unable to connect for backup
So it sees the device but I can't backup?
[edit]Now I connect to the device, the 'adb reboot' command works and the device responds. it's just the backup command that is not working.
Please help
Click to expand...
Click to collapse
i am not at my computer to post the commands, but you can type the commands to backup your system (or dump it) from a androids term console, you need busybox installed
edit: try this link
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
;;
Sent from my Full AOSP on Rk29sdk using xda premium
---------- Post added at 03:40 AM ---------- Previous post was at 03:25 AM ----------
Beeg Boy said:
Where can we find this?
Is there a download link?
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
Hello,
So SuperOneClick did work for you?
What kind of tablet do you have?
What version of Android was it running when you used SuperOneClick?
Thank you,
Click to expand...
Click to collapse
yes it worked for root, my chinese phone just shows Full AOSP on Rk29sdk
Sent from my Full AOSP on Rk29sdk using xda premium

carl1961 said:
i am not at my computer to post the commands, but you can type the commands to backup your system (or dump it) from a androids term console, you need busybox installed
edit: try this link
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Click to expand...
Click to collapse
The thing is I don't have access on my tablet. It won't boot.
So I can't start an app from the tablet, or maybe I can?

Link: USB Driver for T-Mobile SGH-t769 Samsung Galaxy S Blaze 4G

http://org.downloadcenter.samsung.c...113815/T-Mobile_T769_Blaze_4G_USB_Drivers.exe

22.8MB file installing slowly?
First off, I apologize for being paranoid. I downloaded this file and started installing it. It's a 22.8 MB .exe file. I started installing, and it *seems* to be working correctly. After clicking install MSS Installation Wizard is installing Samsung USB Driver for Mobile Phones V1.3.2200.0. Slightly after, desktop toolbar icon popped up Installing device driver software, opened it up showing:
USB Composite Device Ready to use
USB Mass Storage Ready to use
CDC Cerial Waiting for user input
Samsung LTE USB Device Ready to use
Samsung LTE Card USB Device Ready to use
It's been like 10-15 minutes and the MSS Installation Wizard is chugging along, at about 50%. Is this file legit? Is it just my slow ass computer that is making this install take forever? Have other successfully installed this for ADB usage?

Looks to just be the link to Samsung, which yes I have installed. It was a bit slow on my netbook.
Sent from my SGH-T769 using Tapatalk 2

Same here. I installed it yesterday while working on my wife's phone (Blaze also). The first time I tried to install it on my desktop it was slow and there was some sort of error. I had to reboot and redo it before I got it properly installed.

I've never needed the drivers, just downloaded kies.
Sent from my SGH-T769 using XDA

Kies I think installs the drivers for you. You can't properly use the device without the drivers and you definitely cannot use some of the tools without them.

No ADB
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.

Does anyone know how to get this device working with adb on Debian? I can't for the life of me get the device recognized by adb. I have a 51-android.rules set up and all that jazz. udev sees it and rules are applied properly. I just can't get it recognized. It seems references to accessing this device from Linux are very few and far between. What gives?

Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10

strungoutfan78 said:
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
Click to expand...
Click to collapse
Can you explain this a bit more, like where to input these commands. Im a bit green and having this issue.
---------- Post added at 01:25 AM ---------- Previous post was at 01:04 AM ----------
theshowman said:
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Click to expand...
Click to collapse
I tried the #7284# and #9090# and got "unable to process request"
any other suggestions?

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.