Related
So I been trying to use the Sideload Wonder Machine for my Xperia x10 and for some reason the SWM is not recognizing my phone is just doesn't display the device number, I'm pretty sure I have the right drivers I don't know what else to do ? I am getting so frustrated help? why wouldnt SWM reconigze my phone? but the computer does
I had a problem at first and I reinstalled the drivers a couple of times and also used ADB directly and it started working. It's definitely driver and ADB related.
Also, be sure you have debugging turned on in the phone. Once you get it working it should work from that point on.
naplesbill said:
I had a problem at first and I reinstalled the drivers a couple of times and also used ADB directly and it started working. It's definitely driver and ADB related.
Also, be sure you have debugging turned on in the phone. Once you get it working it should work from that point on.
Click to expand...
Click to collapse
Yea I have the debbuging on , and sorry for been so slow lol but mmm I did the same thing unistall and reinstall and it just doesnt work, but what do you mean by the ADB directly? I think thats the one I am using, I mean isnt that the one when you plug your usb cable for the first time it installs itself?
Ladiablae said:
Yea I have the debbuging on , and sorry fo:r been so slow lol but mmm I did the same thing unistall and reinstall and it just doesnt work, but what do you mean by the ADB directly? I think thats the one I am using, I mean isnt that the one when you plug your usb cable for the first time it installs itself?
Click to expand...
Click to collapse
Exact same situation here. Looking forward to the solution.
charlyee said:
Exact same situation here. Looking forward to the solution.
Click to expand...
Click to collapse
Yeah i read your other post, I think it has something to do with the phone, have you try installing and reinstalling the drivers? I have try everything , is getting me upset lol
Ladiablae said:
Yeah i read your other post, I think it has something to do with the phone, have you try installing and reinstalling the drivers? I have try everything , is getting me upset lol
Click to expand...
Click to collapse
Yes I did a few times and no luck.
I read that the Captivate had the same problem and one fix was installing generic Samsung drivers, I am not finding any such thing for Sony. I am convinced it is a driver problem.
charlyee said:
Yes I did a few times and no luck.
I read that the Captivate had the same problem and one fix was installing generic Samsung drivers, I am not finding any such thing for Sony. I am convinced it is a driver problem.
Click to expand...
Click to collapse
Yeah I think so too, I been looking for more drivers and I cant find any.
Have you guys tried killing the PC Companion process (the one that runs on startup) and then trying to reinstall the drivers?
No i have not..but i unistall and reinstall the drivers a lot of times already. I am even lookin for different drivers but they all the same ..or when I try to update it it says that it has the right driver already. I can't think of anything else. I guess. Would never be able to use it
Sent from my X10a using XDA App
I am pretty sure I closed it out, but I will check again.
Thanks.
Same issue with me but doesn't work.
@naplebill - How do you use ADB directly?
Sent from my X10a using XDA App
sopdogg said:
Same issue with me but doesn't work.
@naplebill - How do you use ADB directly?
Sent from my X10a using XDA App
Click to expand...
Click to collapse
You need to download the Android SDK. Once that is setup, ADB is located in the installed folder under the tools folder.
This is a DOS command interface. You will need to run CMD and then from the tools directory type:
ADB shell
This should show the following:
* daemon not running. starting it now *
* daemon started successfully *
If your device is recognized it will show it there as well, if not the last line will be this:
error: device not found
When I download the sdk i need to only installed for the 1.6 version right? I dont need to installed all that crap? Or should i install everythin? I know u hate me am so annoyinnn lol. But am a girl and slow for this kind of things : )
Sent from my X10a using XDA App
Ladiablae said:
When I download the sdk i need to only installed for the 1.6 version right? I dont need to installed all that crap? Or should i install everythin? I know u hate me am so annoyinnn lol. But am a girl and slow for this kind of things : )
Sent from my X10a using XDA App
Click to expand...
Click to collapse
Don't worry, I've been employed in IT for 20 years. It's not because you are a girl, it's because you just don't have the xperience (see what I did there? Lol).
You can just install 1.6, it doesn't matter because you aren't going to use that part of it.
Ohh that's why u know so much about this .... lucky u ...well and about my problem with the swm ..it just doesnt work ...but im tired of tryin everythin so i am gonna wait for the update of 2.1 ..i think with the update would work ....well i hope so hehe
Sent from my X10a using XDA App
Ladiablae said:
Ohh that's why u know so much about this .... lucky u ...well and about my problem with the swm ..it just doesnt work ...but im tired of tryin everythin so i am gonna wait for the update of 2.1 ..i think with the update would work ....well i hope so hehe
Sent from my X10a using XDA App
Click to expand...
Click to collapse
If you decide you can't wait or if it still has issues after the update, I can probably walk you through getting it working via chat or a phone call.
It is definitely an issue with the driver not working with ADB properly. Also, are you killing the process PCCompanion.exe? You can kill this process using Task Manager and clicking on the Processes tab.
Ok, so I've been going back and forth with this too. I had it working, installed SEUS, then it wasn't working, did a system restore, and started over. It was working again. I formatted my phone and noticed it wasn't working again. This is what I did to make it work:
1)Completely uninstall the PC Companion. It's virtually useless now anyway
2)With the phone connected go into the device manager (right click my computer-->Manage and select device manager), and uninstall the device driver windows shows for the phone. As soon as you do that unplug the phone.
3)Go into the C:\Windows\System32 folder and delete these three files (if they are there):
WdfCoInstaller01007.dll
WinUSBCoInstaller.dll
WUDFUpdate_01007.dll
4)If you had the android sdk already just delete the entire folder and download the latest version from here: http://dl.google.com/android/android-sdk_r07-windows.zip
5)Install the packages shown in the attached pic. You only need the 1.6 files and a couple of other packages.
6)Once you get all of this done, plug in your phone with debugging turned on and you should be good to go.
Ladiablae said:
When I download the sdk i need to only installed for the 1.6 version right?
Click to expand...
Click to collapse
See my sig.
Thanks so much SPIDERTECH !! Everything works now!
@Jmercy09 you're quite welcome. I may have to do this again myself. My computer is now, again, not seeing the phone
I actually had to redo these steps and was back up and running. I found the best way to test this after doing the steps is by using the android screencast (attached). If screencast runs and shows your screen, it worked. If it doesn't, then it obviously didn't work as screencast has to see the phone in the same way SWM has to see it.
Im having interesting issues with getting ADB to work...
I believe i have the android SDK installed properly, i can go to the command prompt and do ADB devices no problem, however my phone does not show up. Other guides online said to make sure debugging is on, which it is, but still nothing. Can anyone suggest what i may be missing? have any of you had this problem and know how to fix it?
Try typing "adb fork-server server" then open another window and try connecting with adb again.
Had the same problem. Install Kies and let it download the needed USB drivers; helped me !
[%s] XDA APP SO TASTY WITH MY SLOW INTERNET OMNOMNOM
If i helped you, im sure its not too hard to waste 1 click over that litte pretty "Thanks" Button.
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!!!
Is anybody else having problems with usb debugging mode not working? I have been trying to root with CASUAL all afternoon and I can NOT get usb debugging mode / adb mode to work. Any suggestions on what I could do to make it work?
Thanks guys/girls.
1stx2 said:
Is anybody else having problems with usb debugging mode not working? I have been trying to root with CASUAL all afternoon and I can NOT get usb debugging mode / adb mode to work. Any suggestions on what I could do to make it work?
Thanks guys/girls.
Click to expand...
Click to collapse
I'm having the same issue.. just bought it and this is driving me crazy! I'm i the process of removing drivers and crapware from verizon, and then figured I would try drivers direct from samsung.. I'll let you know if I have any luck.
travisn000 said:
I'm having the same issue.. just bought it and this is driving me crazy! I'm i the process of removing drivers and crapware from verizon, and then figured I would try drivers direct from samsung.. I'll let you know if I have any luck.
Click to expand...
Click to collapse
It's absolutely crazy isn't it? Please let me know if you figure out the problem. I don't consider myself a noob about rooting/romming/etc but this is making me feel like i just started today!
EDIT:::: I finnally got my phone to connect to my moms laptop but it still wont connect to mine. I got CASUAL to recognize the phone but I'm kind of scared to do it now since my first phone connected perfect the first time and when I started having other problems and needed to send it back and usb debugging WOULD NOT work. I don't want to leave it stock but I don't want to go through what I went through with the first phone again
Ok, I finally got my phone rooted, unlocked using casual. I had to use my moms laptop ( hp, windows 7, 32 bit ) to unlock it, our desktop ( windows xp 32 bit ) to use odin and my laptop to transfer music, vidoes, etc..... Now i absolutely hate installing drivers and windows in general. You would think being 1 of the top-of-line smartphones, **** like this wouldn't be so difficult.
It seems this is a driver issue.. I still couldn't get it to work. I'm guessing that either the old GNex drivers or maybe a windows driver. I recall having a similar issue with another device and I had to go through device manager and remove certain drivers and install others.. That doesn't explain the failure I had with linux thought.. perhaps my adb is out of date??
After updating adb removing/installing various drivers in an old XP install was able to get the phone to be recognized by CASUAL, but casual would would reboot the phone to a "Downloading" recovery screen, and just hang.. CASUAL seemed to be waiting for this screen, but could'nt tell that it had it ???
travisn000 said:
It seems this is a driver issue.. I still couldn't get it to work. I'm guessing that either the old GNex drivers or maybe a windows driver. I recall having a similar issue with another device and I had to go through device manager and remove certain drivers and install others.. That doesn't explain the failure I had with linux thought.. perhaps my adb is out of date??
After updating adb removing/installing various drivers in an old XP install was able to get the phone to be recognized by CASUAL, but casual would would reboot the phone to a "Downloading" recovery screen, and just hang.. CASUAL seemed to be waiting for this screen, but could'nt tell that it had it ???
Click to expand...
Click to collapse
Yep that's the same thing that happened on my windows xp based desktop, it would boot into download mode but it wouldn't recognize the phone. It's got to be a driver related issue though. I had similar issues with my gnex but that was nothing compared to this catastrophe.
Sent from my SCH-I605 using Tapatalk 2
I finally got mine done.. gave up on windows drivers and went back to linux.
I had to switch to a disto that used gksudo & dpkg in order for the CASUAL app to work properly (..my distro of choice is PCLinuxOS, but it doesn't use gksudo or dpkg).
So I went on trying the leaked Samsung firmware for my GT-I9300, everything seems fine, may be even better than the last one released here in Mexico, thing is, now that I'm trying to pull some files from my device via ADB it says that it is unauthorized, I searched for a while and I found that there needs to pop a prompt to authorize my PC to connect via ADB, but there's no such prompt. I tried checking/unchecking the USB debug mode on my device, restarting it, re-plugging it, different ports, ADB over the network, restarting my PC, anything that I can think of, and no luck.
Can anyone give me some insight on what can I do?
Thanks in advance and I apologize beforehand for my weird English.
Are you doing it through recovery? Are you rooted? Little more detail would help to get a better answer.
Rooted ?
sent from marijuanated muffin
jhonyrod said:
So I went on trying the leaked Samsung firmware for my GT-I9300, everything seems fine, may be even better than the last one released here in Mexico, thing is, now that I'm trying to pull some files from my device via ADB it says that it is unauthorized, I searched for a while and I found that there needs to pop a prompt to authorize my PC to connect via ADB, but there's no such prompt. I tried checking/unchecking the USB debug mode on my device, restarting it, re-plugging it, different ports, ADB over the network, restarting my PC, anything that I can think of, and no luck.
Can anyone give me some insight on what can I do?
Thanks in advance and I apologize beforehand for my weird English.
Click to expand...
Click to collapse
ME7 is a leak (production build), "adbd cannot run as root in production builds" will always pop up.
i dont know how to fix this, but im pretty sure its a line in the build.prop and something in /system/bin.
ricky310711 said:
ME7 is a leak (production build), "adbd cannot run as root in production builds" will always pop up.
i dont know how to fix this, but im pretty sure its a line in the build.prop and something in /system/bin.
Click to expand...
Click to collapse
I didn't find anything on my build.prop about that, also, no pop up shows, not the prompt to authorize my PC nor the one you mentioned
wangdaning said:
Are you doing it through recovery? Are you rooted? Little more detail would help to get a better answer.
Click to expand...
Click to collapse
No, didn't tried it via recovery, I might try, but it may become a hassle, since I do this frequently. Also, I tried this before and after rooting it with no effect whatsoever.
jhonyrod said:
I didn't find anything on my build.prop about that, also, no pop up shows, not the prompt to authorize my PC nor the one you mentioned
No, didn't tried it via recovery, I might try, but it may become a hassle, since I do this frequently. Also, I tried this before and after rooting it with no effect whatsoever.
Click to expand...
Click to collapse
hmm, theres only one thing that solved this problem, you have to flash a different kernel!