PC: Ubuntu 12.04 with GNOME 3.2 desktop. Phone Galaxy S3 i9300, rooted but running the original stock Samsung.
I have a HTC Desire running Cyanagenmod - it connects to my computer and I have adb access to the command line with no problems at all.
HOWEVER:
Rooted S3: I cannot get it working via adb. I have switched on USB debugging. I've tried rebooting, plugging/unplugging, adb server kill/start to no avail.
As I can't connect, via adb, I tried using an SSH server on the phone and I accessed via the terminal on my PC. That worked but I was surprised to find that I couldn't do anything I wanted via the command line. I tried 'su -' and it was happy with that but whatever I tried to do - including chmod etc, all I got was a response of 'read-only file system' and commands were not effective. On my HTC desire I can do anything on the command line so this was a surprise to me - perhaps it is only possible via adb??
So, in summary, I have two problems:
1. I can't connect via adb when I know it works OK on my HTC Desire.
2. I can't get the root privileges I would expect on the command line.
Any suggestions as to where to go from here will be gratefully received
technoboi2 said:
PC: Ubuntu 12.04 with GNOME 3.2 desktop. Phone Galaxy S3 i9300, rooted but running the original stock Samsung.
I have a HTC Desire running Cyanagenmod - it connects to my computer and I have adb access to the command line with no problems at all.
HOWEVER:
Rooted S3: I cannot get it working via adb. I have switched on USB debugging. I've tried rebooting, plugging/unplugging, adb server kill/start to no avail.
As I can't connect, via adb, I tried using an SSH server on the phone and I accessed via the terminal on my PC. That worked but I was surprised to find that I couldn't do anything I wanted via the command line. I tried 'su -' and it was happy with that but whatever I tried to do - including chmod etc, all I got was a response of 'read-only file system' and commands were not effective. On my HTC desire I can do anything on the command line so this was a surprise to me - perhaps it is only possible via adb??
So, in summary, I have two problems:
1. I can't connect via adb when I know it works OK on my HTC Desire.
2. I can't get the root privileges I would expect on the command line.
Any suggestions as to where to go from here will be gratefully received
Click to expand...
Click to collapse
Did you flash a kernel with adb support?
I always use adb from recovery personally
rootSU said:
Did you flash a kernel with adb support?
I always use adb from recovery personally
Click to expand...
Click to collapse
Ah, in my ignorance - no.
When I first rooted my HTC I put a ROM on it and it worked. I didn't give thought as to the Kernel - I guess I thought it would already be there.
So, it looks as if I need to do some reading and change the kernel. If you have a suggestion for which kernel I will see if I can find how best to install it.
Pretty much any tbh..
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Related
So here is my story; i was planning on selling my prime today. I plan to meet the buyer in an hour. I round up all the accessories and everything. My last step was to completely wipe the device. I wipe everything from cwm touch version. I go to reboot and all it did was reboot into cwm. I have searched up and down to find out how i can get adb to recognize my prime but nothing works at all.
I have the correct drivers installed using universal naked drivers. My computer (windows 7) sees that i have android adb interface. When i go into my cmd prompt and type "adb devices" nothing at all is recognized. When i type "adb shell" it says "error: device not found".
I have tried absolutely everything to get the adb working but it cant seem to see my prime.
If anyone at all can help that would be great. I've heard that manually installing the SDK works but i'm so new to this stuff and would appreciate if anyone could send me a link.
Thank you.
I had the same issue, the universal naked drivers adb didn't work for me, I found an ADB.ZIP earlier in the thread and then it was all smooth sailing. Should fix it for you!
fordwolden said:
I had the same issue, the universal naked drivers adb didn't work for me, I found an ADB.ZIP earlier in the thread and then it was all smooth sailing. Should fix it for you!
Click to expand...
Click to collapse
was it adb.rar? because i tried that one too and it did not work.
I managed to use the vipermod tool to get my pc to recognize the prime by adb. then i went into a different cmd window and followed the instructions in the OP. everything works like a dream now.
I can't seem to work ADB or anything like that, I've read most of the threads on here and tried to follow numerous tutorials and this is my first android phone.
I've enabled USB Debugging, however when I run install.bat with superuser.apk in the same folder it just tells me that there is no device found, not sure what to do
-thanks
I had a similar issue. Easiest thing to do is install omega .
Make a back up of your stock Rom first then flash omega without wiping your data.
It has full root built in
Sent from my GT-I9300 using Tapatalk 2
Your problem is you need to run adb start-server in a terminal in the sdk/platform folder.
It needs to start so the install bat can talk to the phone.
Had the same issue yesterday in my case there was a strange problem with the drivers. All was installed fine i could see ADB device in device manager however adb did not se the device.
Finally installed kies on a computer that never had anything installed like mobile phones etc than run install.bat and all was ok.it took around 15 sec to find the phone and drivers and finish all the rooting operations.
Still dont know what kind of a driver conflict is it...Some report that reinstalling kies helps but not in my case.
If u can try on another computer.
Hey guys
I've been trying to run ADB on my mac and it starts up but it won't recognize my phone, I run a parallel on my mac and I can run ADB on my windows parallel but when I switch over to my mac it won't recognize it for some reason when I go into 'system report' it show's my phone there but when I run ADB in terminal it doesn't show my device... I've been to
http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/
http://forums.androidcentral.com/th...9-mac-procedure-how-root-htc-thunderbolt.html
http://forum.xda-developers.com/showthread.php?t=1387527
http://blog.wapnet.nl/2011/05/setup-adb-and-fastboot-with-android-sdk-on-mac-osx
I've tried everything and adb just won't recognize my phone, I have debugging on and make sure I have enough batter life...
I'm running Lion 10.7.4, I can fastboot without any difficulty but not ADB...
does anyone have any idea about what could be wrong or how I can update my drivers on my phone maybe?
THANK in advance!!!
RMseth said:
Hey guys
I've been trying to run ADB on my mac and it starts up but it won't recognize my phone, I run a parallel on my mac and I can run ADB on my windows parallel but when I switch over to my mac it won't recognize it for some reason when I go into 'system report' it show's my phone there but when I run ADB in terminal it doesn't show my device... I've been to
http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/
http://forums.androidcentral.com/th...9-mac-procedure-how-root-htc-thunderbolt.html
http://forum.xda-developers.com/showthread.php?t=1387527
http://blog.wapnet.nl/2011/05/setup-adb-and-fastboot-with-android-sdk-on-mac-osx
I've tried everything and adb just won't recognize my phone, I have debugging on and make sure I have enough batter life...
I'm running Lion 10.7.4, I can fastboot without any difficulty but not ADB...
does anyone have any idea about what could be wrong or how I can update my drivers on my phone maybe?
THANK in advance!!!
Click to expand...
Click to collapse
I am EXTREMELY unfamiliar with a MAC computer, but I imagine it would have a command prompt like program. I believe it's called "Terminal" on MAC.
Have you tried manually running adb through terminal with a command?
Or is it just a problem within the phones adb?
Tried putting your phone on USB mass storage like mode, such as mount as disk drive?
Just trying to think of some things off the top of my head.
ya I've been using terminal and ADB shows that it starts up perfectly like my windows side. I can run fastboot commands with no problem, I've hooked my phone to the computer regularly and also as a mass storage device and ether way it doesn't recognize it.
I think it is something wrong with the ADB code on my phone because I was able to run adb with my brother's phone and my mac recognized it. his phone is stock he hasn't rooted it or anything...
RMseth said:
ya I've been using terminal and ADB shows that it starts up perfectly like my windows side. I can run fastboot commands with no problem, I've hooked my phone to the computer regularly and also as a mass storage device and ether way it doesn't recognize it.
I think it is something wrong with the ADB code on my phone because I was able to run adb with my brother's phone and my mac recognized it. his phone is stock he hasn't rooted it or anything...
Click to expand...
Click to collapse
That's pretty strange. Have you tried flashing to another ROM?
Ya I flashed by to my stock rom and it still didn't want to run... I flashed to an MIUI rom and it didn't want to recognize it ether... so I don't know what's going on... I did unlock my phone using the HTC method, but I did it through my windows side so that might be the reason because it was flashed under windows instead of mac, I don't know if that would really make a difference since it's the same language for fastboot and ADB... what do you guys think? if you think if would make a difference then I'll do it but it just takes a LONG time to run you have to lock the bootloader and then unlock it again, wipes all my data and then I have to reload everything over again... so if you think it would make a difference I'll definitely try it.
Did you get s off before you tried flashing roms? I know that miui is packaged with a custom kernel and you can't flash roms in recovery that have a custom kernel with s on.
Sent from my ADR6400L using Tapatalk 2
no I don't have s off, but I do have an unlocked bootloader and through adb and fastboot I can flash custom kernels, right now I have imoseyon-6.1.AOSP+root and running liquid Gingerbread 3.2 ROM, Android 2.3.7, with the tbolt's update a few months ago HTC locked down the Bootloader and there's no new program like revolutionary to unlock the new bootloader that I know of... I can change everything on my phone except the Radio, but it's through ADB and fastboot you just have to know the codes and what you're doing haha! I've been able to do all that through my windows parellel but I want to get away from that so I can develop everything through my mac OS which is suppose to be easier, from what I read and hear.
Hmmm... I have heard linux is but not mac. I dunno maybe you're right.
Sent from my ADR6400L using Tapatalk 2
Maybe you should try flashing back through windows.
I suppose it wouldn't hurt anything. I'm sure it's worth a shot anyways.
RMseth said:
...with the tbolt's update a few months ago HTC locked down the Bootloader and there's no new program like revolutionary to unlock the new bootloader that I know of...
Click to expand...
Click to collapse
You can S-OFF with the latest update. I have a windows tool that automates most of it.
so I relocked my bootloader with my windows and then unlocked it again through my MAC and the ADB still doesn't want to recognize my phone through terminal, it shows it on my system info just not through ADB...
trter10- you can!!!??? SA-WEE-TA!!! what's the link?
RMseth said:
so I relocked my bootloader with my windows and then unlocked it again through my MAC and the ADB still doesn't want to recognize my phone through terminal, it shows it on my system info just not through ADB...
trter10- you can!!!??? SA-WEE-TA!!! what's the link?
Click to expand...
Click to collapse
Link in my sig. You will have to relock and ruu before it works though because just relocking causes a security warning
Sent from my ADR6400L using Tapatalk 2
What to you mean relock and RUU?
RMseth said:
What to you mean relock and RUU?
Click to expand...
Click to collapse
Relock the boot loader and flash a pg05img to 2.11.605.19. Problem is that it wipes data
Sent from my ADR6400L using Tapatalk 2
1. Make sure parallells is closed so it doesn't steal your connection.
2. cd to the directory platform-tools
3. Type ./adb devices
I didn't see if you confirmed Parallels being closed or not.
OK I FIGURED IT OUT!!!! oh my goodness!!!! this was soo easy and I totally bashed my head in when I finally figured it out!!! oh my goodness!!!!
I had debugging on but I didn't have "unknown sources" marked!!! oh my goodness!!! so when I had both of those marked then it pulled my device right up on my MAC!!!
well for all of those that tried to help me thank you very much!!! I hope you all have a good day!!!
As the title states when I run adb devices it returns an empty list. I have USB Debugging on. I am at a loss here. I have also uninstalled the drivers and tried to push the Google drivers in SDK. That still didn't work. Any advice would be much appreciated.
Thanks
Toggle debugging on then off.
I am in the same boat as you. A suggestion was posted in my thread in the Q&A section that PDANet solves the issue as it installs the drivers for you but it didn't work for me. Any dev's know a solution to this issue.
"fastboot devices" should work.
orangechoochoo said:
"fastboot devices" should work.
Click to expand...
Click to collapse
mine does it gives me the serial number and fastboot
but neither of our adb devices work.
I did the USB Debugging toggle multiple times and and it won't work. I saw your thread termin8tor22 and I am in the process of trying the pdanet solution. I'll post back if it works for me.
orangechoochoo said:
"fastboot devices" should work.
Click to expand...
Click to collapse
When you say that it should work, are you referring to the fact that we can run the exploit and unlock the phone even though it doesn't show in adb devices? I haven't been able to get mine to work that way. Thanks.
The pdanet didn't work either same error as previously stated. Mine doesn't even show up in fastboot devices. I am at a total loss here. I tried to override the drivers and it fails and states that the MTP USB Drivers are the most up to date and refuses to change or update it.
antnyh said:
When you say that it should work, are you referring to the fact that we can run the exploit and unlock the phone even though it doesn't show in adb devices? I haven't been able to get mine to work that way. Thanks.
Click to expand...
Click to collapse
No, the exploit will not work if your phone does not show up in adb.
Also, this thread should be in Q&A, not in Development.
antnyh said:
As the title states when I run adb devices it returns an empty list. I have USB Debugging on. I am at a loss here. I have also uninstalled the drivers and tried to push the Google drivers in SDK. That still didn't work. Any advice would be much appreciated.
Thanks
Click to expand...
Click to collapse
I was able to get it to see the device after going into cwr. then i was all good
jsa11ey001 said:
I was able to get it to see the device after going into cwr. then i was all good
Click to expand...
Click to collapse
How can we get cwr whithout an unlocked bootloader or root. This isn't helpful unless we have cwr already on there which we don't as we don't have root because we don't have adb to push the exploit. I don't mean to be rude but I am getting aggravated with this ADB thing.
CastleBravo said:
No, the exploit will not work if your phone does not show up in adb.
Also, this thread should be in Q&A, not in Development.
Click to expand...
Click to collapse
The thread is where it is unless a mod wants to move it.
jsa11ey001 said:
I was able to get it to see the device after going into cwr. then i was all good
Click to expand...
Click to collapse
I am trying to unlock it so I can get CWR on it. I can't even unlock it since it refuses to show up in ADB. How did you get CWR on yours if you don't mind me asking?
antnyh said:
The thread is where it is unless a mod wants to move it.
I am trying to unlock it so I can get CWR on it. I can't even unlock it since it refuses to show up in ADB. How did you get CWR on yours if you don't mind me asking?
Click to expand...
Click to collapse
I pushed thru adb. did you uninstall htc sync and update your android sdk. sorry just trying to give any usefull info. not in any way a master dev or anything
---------- Post added at 06:43 AM ---------- Previous post was at 06:35 AM ----------
i used this method http://forum.xda-developers.com/showthread.php?t=1996389, and had to do the CIDGEN unlock because I have a verizon phone. I followed the steps exactly and had 0 problems.
see you pushed through adb, which we cant get to recognize our devices. thats all, no harm intended.
antnyh said:
The pdanet didn't work either same error as previously stated. Mine doesn't even show up in fastboot devices. I am at a total loss here. I tried to override the drivers and it fails and states that the MTP USB Drivers are the most up to date and refuses to change or update it.
Click to expand...
Click to collapse
did you change your environment variable path set to your adb/fastboot location?
As for the drivers:
HTCDriver.RAR > run the exe
HTCDriver.rar
HTC.RAR > put in C:\Program Files\ and C:\Program Files (x86)
HTC.rar
thats my setup and it worked
antnyh said:
As the title states when I run adb devices it returns an empty list. I have USB Debugging on. I am at a loss here. I have also uninstalled the drivers and tried to push the Google drivers in SDK. That still didn't work. Any advice would be much appreciated.
Thanks
Click to expand...
Click to collapse
Hello,
I had similar issues with ADB not recognizing the DNA, I disabled HTC sync and closed out of the HTC SYNC in the task manager... You may or may not have tried this... Based on my experience this was what happened with me.. I also have windows 8 64bit. Hope this helps
:fingers-crossed:
I installed drivers listed on one of the forums here. then i installed htc sync. Then i had to download the sdk /with google drivers.
I would assume that when you have your command prompt open that you cd into the folder. platform-tools. that way the cmd can find adb?
kraziekc said:
Hello,
I had similar issues with ADB not recognizing the DNA, I disabled HTC sync and closed out of the HTC SYNC in the task manager... You may or may not have tried this... Based on my experience this was what happened with me.. I also have windows 8 64bit. Hope this helps
:fingers-crossed:
Click to expand...
Click to collapse
Hmm.. I haven't started mine yet but I'm on win8, this seems like good advice. Will be trying later and post results
Sent from my HTC6435LVW using Tapatalk 2
damagickid said:
I installed drivers listed on one of the forums here. then i installed htc sync. Then i had to download the sdk /with google drivers.
I would assume that when you have your command prompt open that you cd into the folder. platform-tools. that way the cmd can find adb?
Click to expand...
Click to collapse
If you set up adb right you don't have to CD into that folder.
Sent from my HTC6435LVW using xda app-developers app
You need to disable HTC Sync. Go in task manager and see if there is another ADB current running. That is what happened to me, HTC Sync was trying to push via ADB so when I tried to root it couldn't recognize my DNA.
Hey guys. I'm trying to root my m8 by using the toolkit. Well, I try to get the Token ID but adb fails since it can't find any devices. I've uninstalled the drivers, re installed, tried different sources, everything and I just can't get it to be recognized by ADB.
Anybody have any ideas? I'm running Win8x64
Regards
Smith
I'm having the same problem
smithisize said:
Hey guys. I'm trying to root my m8 by using the toolkit. Well, I try to get the Token ID but adb fails since it can't find any devices. I've uninstalled the drivers, re installed, tried different sources, everything and I just can't get it to be recognized by ADB.
Anybody have any ideas? I'm running Win8x64
Regards
Smith
Click to expand...
Click to collapse
Make sure your SDK is up to date, and that you are opening the command prompt from the proper location. Also make sure that USB debugging is enabled in developer options on the device.
I've had the same issue. I did all of the above and even tried on a Mac and adb still hasn't recognized my phone. Im on win 7x64. Still researching for an answer.
I'm not sure if this will hold true for everyone, but what worked for me was to updat the adp.exe and dlls. Then after I did that, ran the get token script from the toolbox, open the phone to the home screen, and accept the connection request from the computer.
I ended up having to just start the process over again on a different computer, but it worked, so I'm happy lol.
Regards
Smith
You can also try disabling USB Debugging and re-enabling it while the USB is connected. Works for me so far