Database Develop

[Q] Problem rooting Stock froyo captivate

Hi All,
I just purchased my Captivate yesterday from Costco (Expecting to still get the 2.4 Eclair) but unfortunately I got the Froyo 2.2 on my new captivate.
I tried rooting it using superoneClick and it just gets stuck on "Waiting for Device". I have drivers properly installed on my windows 7 64 bit machine (because I can use the phone and access its internal SD card).
Can anyone have suggestion or faced similar problems?
I have tried disabling/re-enabling usb debgging while it says "Waiting for the device"

Search the forum. There are a few threads floating around on different ways to root the stock froyo build. I don't know why the superoneclick wont work in your case but a search will turn up some info for you.

thanks. I will search the the threads and will post my results here in this thread for someone like me struggling with the same problem.

If you were planning on flashing a custom ROM after rooting anyway, you could use Odin one-click from download mode to flash 2.1 eclair, and then go from there.

Are you sure you are enabling debugging? I just used superoneclick on my phone last night after I flashe dback to stock.
First thing I do is change the phone in settings to - Ask on Connection, then I enable debugging.
Also you could try a different USB port on your computer and also make sure you have all of your necessary drivers installed.
I hope you get it figured out!

PeteSeiler2010: I haven't tried different USB port yet. I will try tonight and see if it goes through.
For usb debugging, I tried that as I mentioned. Let me just conform what I did. When it says "Waiting for device" for several seconds, I disconnected USB cable from either phone or computer (because it says that if you are stuck on "waiting for device", disable and re-enable usb debugging) because without disconnecting the cable, phone didn't let me disable the USB debugging..
So looks like I am missing something here??

22andy2 said:
PeteSeiler2010: I haven't tried different USB port yet. I will try tonight and see if it goes through.
For usb debugging, I tried that as I mentioned. Let me just conform what I did. When it says "Waiting for device" for several seconds, I disconnected USB cable from either phone or computer (because it says that if you are stuck on "waiting for device", disable and re-enable usb debugging) because without disconnecting the cable, phone didn't let me disable the USB debugging..
So looks like I am missing something here??
Click to expand...
Click to collapse
want a much easier method? install speedmod kernel using odin, reboot into recovery, advanced features (not the CWM version), and choose the option that says something like "root phone" and choose the "simple" option. congratulations, you are now rooted and running a custom kernel with CWM that can install a custom ROM.
next time, please do not post this in development as this has NOTHING to do with development. Q&A or general next time, please.

How did someone with no posts, post a question in this section? I thought you had to have a minimum of 10 posts to post in here.

I am sorry if I have missed that rule for the new posting but I am new (just two days old) into the android world and for the xda forums as well..

22andy2 said:
I am sorry if I have missed that rule for the new posting but I am new (just two days old) into the android world and for the xda forums as well..
Click to expand...
Click to collapse
So why is your join date Dec 2007?

CB650 Wolf said:
So why is your join date Dec 2007?
Click to expand...
Click to collapse
thats when I just registered.. I will be the active member now as I officially own the android phone.
I really appreciate all of you guys work and I didn't mean to offend any one by posting the thread here.
I already apologize for missing the rule for the 10 minimum posts on forum before posting.

I rooted my device successfully by using odin. Thanks all of you for the suggestions.

[Q] computer can't see Galaxy S

my samsung galaxy s is not recognized by my computer no matter what i do!
don't know why, i've done some research, no results.
i've installed Kies, which i assume already installs the drivers, but when i connect, the computer shows no sign of connection (it says that i need to update drivers in device manager??) i tried different USB ports, toggled USB debugging on/off, NOTHING WORKS
the reason i want my computer to recognize the galaxy is because i want to update it to android 2.3.5 via odin. but when i enter download mode, the computer doesn't recognize it. when i'm in the system, the computer STILL doesn't recognize it...???
please somebody help, it's rooted, running a different MIUI version (not the ones in xda dev section), i'm not sure where i got it from, but it's called an ENG_MIUI?

CM7 (and subsequently MIUI) is built from the Nexus S source code, so find the proprer drivers for it. "CM7 drivers" should be a sufficient google search. Also, Kies sometimes interferes while using the other drivers. If you run into any problems, uninstall Kies.

Okaham said:
my samsung galaxy s is not recognized by my computer no matter what i do!
don't know why, i've done some research, no results.
i've installed Kies, which i assume already installs the drivers, but when i connect, the computer shows no sign of connection (it says that i need to update drivers in device manager??) i tried different USB ports, toggled USB debugging on/off, NOTHING WORKS
the reason i want my computer to recognize the galaxy is because i want to update it to android 2.3.5 via odin. but when i enter download mode, the computer doesn't recognize it. when i'm in the system, the computer STILL doesn't recognize it...???
please somebody help, it's rooted, running a different MIUI version (not the ones in xda dev section), i'm not sure where i got it from, but it's called an ENG_MIUI?
Click to expand...
Click to collapse
To get your phone recognized you need nexus s drivers. But that won't help you get it recognized by kies.
You need stock firmware on your phone to get it updated through kies.
Sent from my GT-I9000 using xda premium

I have same problem previously. But it solved after I do this: while Kies open, select Tools then press Install driver.

thanks guys, but how would i go about doing that? the directions i found don't make any sense?

ndemin said:
I have same problem previously. But it solved after I do this: while Kies open, select Tools then press Install driver.
Click to expand...
Click to collapse
Just to clarify, this won't help you. Samsung uses Samsung drivers. Since you do not currently have Samsung firmware on your phone, this won't do you any good. As previously stated by two very informative posters, you will need the Nexus S drivers to recognize your phone.
And, also as previously stated by just an absolutely wonderfully helpful poster, if you do a simple google search you'll find exactly what you need. Try either Nexus S Driver, CM7 Driver, Nexus S CM7 Driver, or really anything else similar. You could also check the CM7 Wiki, as I'm sure there would be a link for them there. And finally, if you simply search XDA Developers, I'm sure you'd find plenty of posts with what you need.
Hopefully that helps.

thanks
now my computer can see it when it's in android, but why does it STILL not see my Galaxy S in download mode???
do i need another set of drivers? (it said driver not found)
BTW THANKS GUYS!!! sorry if i'm being annoying

hello??
anybody??

Well did you install the Nexus S drivers yet?

upichie said:
Well did you install the Nexus S drivers yet?
Click to expand...
Click to collapse
yes, the nexus s drivers are installed, but i STILL can't connect through download mode...

try different computer, install samsung driver then connect your phone

still doesn't work???

Well, it seems to be a driver issue!
Try these (32-bit windows) but make sure that you are having a fresh win7 installed just in any case that your reg got corrupted with drivers (Ime ).
Still not working,then try on another pc..!
---------- Post added at 07:12 AM ---------- Previous post was at 07:06 AM ----------
upichie said:
Just to clarify, this won't help you. Samsung uses Samsung drivers. Since you do not currently have Samsung firmware on your phone, this won't do you any good. As previously stated by two very informative posters, you will need the Nexus S drivers to recognize your phone.
And, also as previously stated by just an absolutely wonderfully helpful poster, if you do a simple google search you'll find exactly what you need. Try either Nexus S Driver, CM7 Driver, Nexus S CM7 Driver, or really anything else similar. You could also check the CM7 Wiki, as I'm sure there would be a link for them there. And finally, if you simply search XDA Developers, I'm sure you'd find plenty of posts with what you need.
Hopefully that helps.
Click to expand...
Click to collapse
Well, CM7 drivers won't help SGS to get recognized on PC on DLD mode, you need another set of drivers and not those Nexus S's. I had the above ones installed on my PC (Google's your Best friend ) .

I had to install the drivers manually,
Right click on computer, click manage -> device something -> find your device in the list, select to update driver, search manually and enter the path to your android sdk and search.
Worked like a charm to me
Sent from my GT-I9000 using XDA App

pzayx said:
I had to install the drivers manually,
Right click on computer, click manage -> device something -> find your device in the list, select to update driver, search manually and enter the path to your android sdk and search.
Worked like a charm to me
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
computer could see device in download mode?

hi
i had same problem, but computer recognize the device as "unknown device"
in all modes, developed, storage etc...
i am close to think thats is problem of internal usb driver of the rom
want to downgrade from de device, whitout usb, but i dont know how do it, because i am not root, and its no possible in 2.3.4 whituot usb.
thanks

I had a lot of similar issues with my I9000, too.
Tried everything on ROM and driver side also on different computers.
Finally it turned out that my Micro USB connector was corroded.
I have around 30 people in our company that have the same phone, and 5 of them had similar issues. I guess it's a common problem with this device.
I took a toothpick and cleaned the contact of the connector by sliding it up and down for a couple of million times. This also did the trick for my colleagues.
I think it's at least worth to try it.
Good luck

i try to clean the contact, but still cant connect to the computer.
I wonder if a method of degrading the system with a signed rom from the recovery, without using the USB cable or ODIN.

i have a same problem. Any new solution?

snbmf said:
i have a same problem. Any new solution?
Click to expand...
Click to collapse
use this guide
Check this out! Links to useful Guides and " Banned " Documentaries ​

Drivers Tried everything!

I have spent Friday and Saturday trying to get drivers installed on my Nexus 6. I have removed, uninstalled, added Google drivers, added sdk adb, computer needs to be returned Monday and this new Toshiba Satellite with one usb port with not recognize my phone. Even though the computer beeps every time I plug it in or out.
Any steps or detailed procedures would be greatly appreciated. Thank you!
Sent from my SGH-I337 using Tapatalk

Try using the Wug Fresh Root Toolkit in the Development section for the Nexus 6. Just make sure you follow the instructions. There are several different ways to find the correct drivers with his Toolkit. Good luck!

dave2metz said:
Try using the Wug Fresh Root Toolkit in the Development section for the Nexus 6. Just make sure you follow the instructions. There are several different ways to find the correct drivers with his Toolkit. Good luck!
Click to expand...
Click to collapse
Thanks man, but that's how I unlocked and rooted my phone. It's also how I screwed my phone up, trying to undo the forced encryption. Did it all with Wug's Nexus Tool Kit. I have been at this 25 hours with no success. Drivers are needed. I don't know why the computer doesn't recognize the phone, the computer beeps every time I plug it in or unplug it.
Sent from my SGH-I337 using Tapatalk

addcancercat said:
I have spent Friday and Saturday trying to get drivers installed on my Nexus 6. I have removed, uninstalled, added Google drivers, added sdk adb, computer needs to be returned Monday and this new Toshiba Satellite with one usb port with not recognize my phone. Even though the computer beeps every time I plug it in or out.
Any steps or detailed procedures would be greatly appreciated. Thank you!
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I always have issues with Nexus devices being recognized. I always have to plug the device in, go to the device manager, and delete anything that has to do with the device, including any labeled as ADB devices. I've also found it helps to go to "View" and hit "Show Hidden Devices". After deleting them all, I unplug and replug the device and install the Universal Naked Driver from this thread.

addcancercat said:
I have spent Friday and Saturday trying to get drivers installed on my Nexus 6. I have removed, uninstalled, added Google drivers, added sdk adb, computer needs to be returned Monday and this new Toshiba Satellite with one usb port with not recognize my phone. Even though the computer beeps every time I plug it in or out.
Any steps or detailed procedures would be greatly appreciated. Thank you!
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I assume with it being a Toshiba Satellite its running windows, what version? The older OS's seemed to be less finicky then W8, Have you deleted and re-installed the google drivers from http://developer.android.com/sdk/win-usb.html or from another site? Have you tried any different PC's? Have you checked the windows hardware event logs for any error messages? Have you been able to put in say a thumb drive into the usb port and it work? Are you on as admin and all that security crap? Do you have usb debugging on in the developer area on the phone? Are you able to get it into fastboot mode? If you do fastboot devices does it show anything at all? I assume you have rebooted the PC, but I'm still surprised how many issues that fix's.
Just some suggestions, I know how frustrating it can be. Good luck.

Thanks. I did that and I downloaded an Intel driver so now the computer recognizes the phone in Device Manager.
Sent from my SGH-I337 using Tapatalk

jackpollard said:
I assume with it being a Toshiba Satellite its running windows, what version? The older OS's seemed to be less finicky then W8, Have you deleted and re-installed the google drivers from http://developer.android.com/sdk/win-usb.html or from another site? Have you tried any different PC's? Have you checked the windows hardware event logs for any error messages? Have you been able to put in say a thumb drive into the usb port and it work? Are you on as admin and all that security crap? Do you have usb debugging on in the developer area on the phone? Are you able to get it into fastboot mode? If you do fastboot devices does it show anything at all? I assume you have rebooted the PC, but I'm still surprised how many issues that fix's.
Just some suggestions, I know how frustrating it can be. Good luck.
Click to expand...
Click to collapse
No, I have a Nexus 6 that the computer won't recognize. ADB and SDK also don't recognize the phone.
I am using my old Samsung S4 for emergency support. It's not hooked up with AT&T since I got the Nexus 6. I have to return this computer tomorrow. I am starting to wonder if it's computer problems with phone problems.
Sent from my SGH-I337 using Tapatalk

When you type ADB command in the DOS Box, there should be a popup on the mobile whether you wanna allow access from this computer.
Did you select yes and remember that PC?

I had this problem when I did my nexus 6, something on the laptop I was using was conflicting, I moved to another laptop and it worked like a charm never went back to figure out what was conflicting. Do you have access to another machine?

[Q]ADB/Device Manager Issues, help please!

Hello all, first time poster, but I have been lurking for a few days absorbing what I can. I just recently got my first Android phone, the Droid Turbo. So far I love it. I am trying to use the awesome Debloater tool I found elsewhere, but I have a problem. When ever I connect my Droid Turbo to a computer in my house (desktop or laptop), I get an error in device manager. Neither the standard Google ADB driver, or the Universal ADB drivers seem to be working. I am not stupid when it comes to computers, but am I missing something? I have uninstalled, restarted and reinstalled both drivers a few times, I even tried using the SDK to install Google's drivers as well. USB debugging is turned on. I can't seem to find any USB drivers for the Droid Turbo at the Motorola site listed with Google. The phone is new, running 4.4.4 KitKat. I am running Windows 7 x64 on my PC, a fairly fresh install. I'm really at a loss to figure out what is going on, any help or a point in the right direction would be greatly appreciated . I have already searched most of the relevant information and videos on this sight, but perhaps I missed something.
Please keep up the good work! My phone is just begging for a root/unlocked bootloader with a clean Android install, But I will settle for no bloatware for now.
I was going to include a screenshot of what I see with my phone plugged in, but I don't have enough posts yet. None of the options of "Update Driver" result in it working, its as if it sees my Droid Turbo there, but I just don't have correct the drivers for it, and I cant find the right ones.

Install drivers from motorola and select driver manualy, dont work with Windows XP

matheus_sc said:
Install drivers from motorola and select driver manualy, dont work with Windows XP
Click to expand...
Click to collapse
at this link:
Motorola Device Manger/USB drivers.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481

Awesome!
Awesome! That link is what I was missing. Thanks a lot to both of you!

Can't get Oneplus 3T recognized via ADB

I'm sure I'm not the only person who's had this issue but I've read through a bunch of threads and can't seem to find any that mirror the issues I'm seeing.
I downloaded the latest google drivers here:
https://developer.android.com/studio/run/win-usb.html
I changed the USB mode from charging to file transfer (not sure if that matters but one of the threads said this helped discover the ADB device needs, which was the case for me)
When I look at the device manager, I see this:
http://pasteboard.co/5UkUolhM2.png
I actually thought I was going to see this (based on a few user posts I read) but no luck . . .
http://pasteboard.co/5Uo9QvP8z.png
I hate asking such a basic question (I'm trying to root my phone but I'm already stuck at the backup stage . . . heh) but I've honestly tried to look through the threads and resolve it but I haven't found a solution yet. It doesn't mean one doesn't exist (I apologize if one does, I honestly have tried to solve this myself).
I apologize for the links rather than pics but it doesn't seem to want to let me use the IMG tags (do they not work with *.png?).
Any help you can give me would be greatly appreciated. Thanks!

I have a somewhat similar problem. Which I can attribute to some sort of driver/inf screw up
Any device i connect to my Win 10 PC in MTP mode gets recognized in device manager as MTP device and I can't do anything about it.
Unless I go back to driver setting, have it automatically find updated drivers, which it doesn't.
But then right after, if i go to manually select driver and switch it from MTP to MTP USB - it fixes everything
Any idea how to fix that. I'm sure it's a similar issue to this.

I couldn't use the Google drivers, I had to use the OnePlus Driver package.
Beside, did you guys enable USB debugging?
Cheers
Tom

if device manager is showing any unknown devices then start with that when you can plug in the phone without problems have a look at this.
https://forum.xda-developers.com/showthread.php?t=2317790

Which adb version do you use?
Sent from my ONEPLUS A3003 using Tapatalk

I've actually tried installing those drivers (on the partition), the google drivers, a fastboot and ADB program, and even an all in one tool for drivers and none of them worked.
That said, I might have found my problem. I've tried several approaches and found out the the virus protection on this computer (Cylance) is blocking everything. Also explains some issues I had getting things to work with some home automation projects . . . I'll have to find another computer for development.
I'll give you guys an update once I have one. Thanks for the quick replies.

I wanted to follow up on this since I got it up and working just fine.
First off, thanks to everyone that helped, either those that provided answers, or those that confirmed they were seeing the same issues.
It does appear that cylance (my antivirus) was blocking a number of things. I have a different laptop with a fresh version of windows 10 (not a requirement, just making note of this) and protected by bit defender and set it up with that. This is what I did:
1) Plug phone into computer
2) Went to pulldown menu, clicked on "charging mode" and changed it to "transfer files"
3) A partition was found on my computer called "Oneplus Drivers" (on the my computer page, next to the C drive). I double clicked on the directory and it installed the drivers to my computer
4) I downloaded and installed Minimal ADB with fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790. (You'll need to click a few links to get to the actual download but I wanted everyone to know that it's a legitimate link and not just my own personal/questionable source)
5) I ran minimal adb and typed "adb devices". It will show your device as "unauthorized" initially because it hasn't been accepted on your device. Open your device and click allow or ok or something to that effect (didn't think to take a screenshot). Your call if you want it to always remember that device.
6) Type "adb devices" again and it should show your device labeled "device"
So yeah, that's how I got the basic ADB up and working. Hopefully you guys resolve this as well. Good luck!

I was too having the same issue but solved using this easy method https://youtu.be/LbAq6d2Du0U

jbrookley said:
I'm sure I'm not the only person who's had this issue but I've read through a bunch of threads and can't seem to find any that mirror the issues I'm seeing. ...
Click to expand...
Click to collapse
Try the ones here? > http://www.technobuzz.net/download-oneplus-3-usb-drivers/

hello2010 said:
Try the ones here? > http://www.technobuzz.net/download-oneplus-3-usb-drivers/
Click to expand...
Click to collapse
I'm confused, I posted a solution to this 2 posts ago. Are these drivers any better than the ones that are on the phone itself as described in my previous post?

jbrookley said:
I'm confused, I posted a solution to this 2 posts ago. Are these drivers any better than the ones that are on the phone itself as described in my previous post?
Click to expand...
Click to collapse
I haven't compared them so I can't comment. The above link was where I learned to install the drivers once (because it worked the first time). If your connection is working fine now, just treat the info in the link as added reference.

hello2010 said:
I haven't compared them so I can't comment. The above link was where I learned to install the drivers once (because it worked the first time). If your connection is working fine now, just treat the info in the link as added reference.
Click to expand...
Click to collapse
Oh, ok! All caught up!

Having the same issue. Didn't have any issue with my old Huawei Ascend Mate 2 though.

j03x2 said:
Having the same issue. Didn't have any issue with my old Huawei Ascend Mate 2 though.
Click to expand...
Click to collapse
Have you tried any of the solutions that were posted?

Didgeridoohan said:
Have you tried any of the solutions that were posted?
Click to expand...
Click to collapse
Problem solved now. For some reason the USB Debugging flag changed without me doing it.