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).
Related
ok, this problem is notorious on my laptop. this time its a little different though. i reset my laptop and put windows 7 on it yesterday. now ive been spending all day personalizing it to my comforts and that includes getting my laptop to connect my phone to ODIN. i ODINed my phone to JT's vanilla GB on my friend's laptop a few days ago and now i want to switch to CM7. I installed both, the Nexus S drivers AND the Samsung drivers and everytime i connect my phone and go into download mode, it fails to connect to ODIN because of the drivers. i dont know what to do but i really want to get this thing working and not worry about these damn drivers anymore! >_< ....please help lol
DroiDAddicT14 said:
ok, this problem is notorious on my laptop. this time its a little different though. i reset my laptop and put windows 7 on it yesterday. now ive been spending all day personalizing it to my comforts and that includes getting my laptop to connect my phone to ODIN. i ODINed my phone to JT's vanilla GB on my friend's laptop a few days ago and now i want to switch to CM7. I installed both, the Nexus S drivers AND the Samsung drivers and everytime i connect my phone and go into download mode, it fails to connect to ODIN because of the drivers. i dont know what to do but i really want to get this thing working and not worry about these damn drivers anymore! >_< ....please help lol
Click to expand...
Click to collapse
What version of odin are u using? For windows 7 I use odin3 v1.7
droidstyle said:
What version of odin are u using? For windows 7 I use odin3 v1.7
Click to expand...
Click to collapse
where can i find that version? lol and idk if that even has anything to do with my drivers not working haha
try the samsung drivers and odin in this link
http://forum.xda-developers.com/showthread.php?t=1238070
ODIN does NOT recognize my Droid Charge
Fist of all let me tell you what I have done to resolve this on my own:
Uninstalled/Re-installed the drivers for the Droid Charge
Put device into USB Debugging mode
Unknown sources are checked
Power cycled
Uninstalled/re-installed ODIN
Tried different pc's (all Windows)
Tried different USB ports on all of the pc's I have used
Factory reset on the device
I have read blogs that other people are having this same issue, suggested those troubleshooting steps, they did not work for others but hey I might get lucky right? And this is still a no go, so could someone PLEASE provide me with the correct troubleshooting steps to take to resolve this?
DroiDAddicT14 said:
where can i find that version? lol and idk if that even has anything to do with my drivers not working haha
Click to expand...
Click to collapse
did you get things working?
I've looked all around for this - I got ADB drivers to install just fine so that's no issue. It's just... for some strange reason my phone works completely fine while plugged in, but the minute you go into fastboot my computer rejects it. I get a pop up saying:
The last USB device you connected to this computer malfunctioned, and Windows does not recognize it.
Click to expand...
Click to collapse
So, of course, I do a little digging and find where my DNA in Fastboot should show up in device manager.. and it says:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
Should I reinstall HTC Sync or something (I uninstalled it)? I'm lost. Can't think of anything to do. Shuffling around the drivers that come with the SDK doesn't help any - and my Windows 7 machine didn't have any of these issues. Too bad it's dead now
[TSON] said:
I've looked all around for this - I got ADB drivers to install just fine so that's no issue. It's just... for some strange reason my phone works completely fine while plugged in, but the minute you go into fastboot my computer rejects it. I get a pop up saying:
So, of course, I do a little digging and find where my DNA in Fastboot should show up in device manager.. and it says:
Should I reinstall HTC Sync or something (I uninstalled it)? I'm lost. Can't think of anything to do. Shuffling around the drivers that come with the SDK doesn't help any - and my Windows 7 machine didn't have any of these issues. Too bad it's dead now
Click to expand...
Click to collapse
Alright, so you're going to want to have HTCSync installed, then after thats done, go to your device manager and select your device (not sure what it will be under, but it will have a (!) sign next to it). Download these drivers and use the "have disk" thing when looking for drivers in device manager. Make sure your DNA isn't plugged into a USB3 port, and then fastboot should work for you.
inexplicability said:
Alright, so you're going to want to have HTCSync installed, then after thats done, go to your device manager and select your device (not sure what it will be under, but it will have a (!) sign next to it). Download these drivers and use the "have disk" thing when looking for drivers in device manager. Make sure your DNA isn't plugged into a USB3 port, and then fastboot should work for you.
Click to expand...
Click to collapse
Ran into this yesterday. My computer ONLY has USB3 so I was unable to get it to work. Tried on a Win7x64 machine and did it first time no problem. Sigh...
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
[TSON] said:
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
Click to expand...
Click to collapse
I don't have any tips for you, other than to say that I've had fastboot work with my DNA on 2 different win 8 64 machines.
I *think* I got my drivers from HTCSync, and then uninstalled HTCSync, but not the drivers afterwards.
I did have problems with fastboot and adb when I was playing around with the CM10 build that is available here. Maybe try switching your rom and kernel?
[TSON] said:
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
Click to expand...
Click to collapse
I ran into the same exact issue on my win8 64-bit machine. luckily i have a couple usb2 ports and they work just fine. i wonder if using a usb hub that is compatible with usb2 or lower would work.
Did you try disabling driver signing in Windows 8 pretty sure thats the problem.
Here
Yeah you have to do that in order to install the universal driver or any other unsigned drivers - but once the drivers are installed you're good to go. No matter which drivers I pick I have this problem, I've tried probably 7 different ones.
Works fine on my Vista laptop but that things about to creak... Just used it to S-OFF and it took over an hour to turn on :crying:
EDIT: And for what it's worth, doesn't matter if it's a USB 3.0 or 2.0 - same error. Doesn't work on stock or on Cubed/Viper (though this is fastboot so kernel/ROM shouldn't have anything to do with 'em).
Computer wont recognize my device anymore. I have downloaded every set of drivers from this forum, from the samsung website, I even tried downloading kies but it wouldnt recognize it either.
It worked before I did the following and now it doesnt.
First I rooted my phone with route 66 everything was going fine until I made the huge mistake (not knowing) and downloaded rom manager so that I could do a nandroid backup. Well as we all know now, you cant do that. So I got the deadly uellow verizon triangle saying unauthorized software bring it to the store. So I went through the xda forums and found the one that told me how to fix it. I used odin with the alternate restore and got it back up and running. So I wanted to go back and use adams one click unlock and root. I got everything downloaded and ready. I put my phone in developer mode and plugged it in. It starts trying to find the drivers and then it flips from debugger mode to media mode everytime. It starts seeing it as everything but a samsung phone. It says found camera and even cd rom but not the phone. I have read through everything and tried everything I could think of but I am at a loss. PLEASE HELP
Sent from my SCH-I605 using xda app-developers app
brandi1693 said:
Computer wont recognize my device anymore. I have downloaded every set of drivers from this forum, from the samsung website, I even tried downloading kies but it wouldnt recognize it either.
It worked before I did the following and now it doesnt.
First I rooted my phone with route 66 everything was going fine until I made the huge mistake (not knowing) and downloaded rom manager so that I could do a nandroid backup. Well as we all know now, you cant do that. So I got the deadly uellow verizon triangle saying unauthorized software bring it to the store. So I went through the xda forums and found the one that told me how to fix it. I used odin with the alternate restore and got it back up and running. So I wanted to go back and use adams one click unlock and root. I got everything downloaded and ready. I put my phone in developer mode and plugged it in. It starts trying to find the drivers and then it flips from debugger mode to media mode everytime. It starts seeing it as everything but a samsung phone. It says found camera and even cd rom but not the phone. I have read through everything and tried everything I could think of but I am at a loss. PLEASE HELP
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Turn off your phone, connect to your computer with the USB cord and turn back on your phone. It should start the drivers and connect to your device.
smalk said:
Turn off your phone, connect to your computer with the USB cord and turn back on your phone. It should start the drivers and connect to your device.
Click to expand...
Click to collapse
I tried that, it is still not seeing it like it is supposed to. I was able to get Odin to recognize it so that I could flash the rooted stock again but I can't get Casual Jailbreak to work. I'm not sure if it is because the drivers or not but I am guessing it has something to do with it. Every time I plug it in, it starts searching for drivers and then always switches from usb debugging mode to media mode. The checkmark is still in usb debugging but I don't think it actually is. You can watch it go from device as installer to media.
Are you using the driver install app (zadig i think its called) to install the heimdall driver on top of "gadget serial". Looking at your other post it seems like a driver issue. One thing ive noticed is, if odin can see the device then heimdalll cant and vice/versa. So if odin can see it you have the wrong driver, if you are infact installing the heimdall driver my second question is, does windows xp x64 use driver sig enforcement like win7 x64 does? if so you probably need to disable it. Just throwing my $0.02 out there.
Are you using the official USB cable? I had an aftermarket cable that had worked for months, then decided to quit working. It works with other devices just not the Note2. Changed to my original cable and all is well.
nunyazz said:
Are you using the official USB cable?
Click to expand...
Click to collapse
Also try plugging it in to the PC and not through a hub/keyboard/monitor port
Sent from my SCH-I605 using xda app-developers app
If it sees the device in the dumb verizon cd mode thing and ptp than it can see adb. Its not the cable. however i would try setting the usb debugging first than set it to camera mode. adb should still be able to pick it up
Thank you everyone for your help, I finally got the drivers working and the bootloader unlocked
brandi1693 said:
Thank you everyone for your help, I finally got the drivers working and the bootloader unlocked
Click to expand...
Click to collapse
How? Fixing to unlock my spanking new note also. I had the drivers issues late last night. When installing drivers through the Z app I never could get it to install Samsung usb drivers nor did I see serial gadget option. Running Windows Vista 64bit. I know I have Java.
Sent from my SCH-I605 using xda premium
hello.
i think i have already tried everything to get fastboot on my pc find my device, but no luck.
I've got an old laptop with usb 2.0 + windows 8.1 x64 Pro and the same OS on my PC with usb 3.0 (according to some of threads, my CPU is i7 4770k and my MOBO is MSI Z87-G45).
I use my HTC Desire X every day and it is simply slow. I cannot try every ROM cause of need to flash boot.img. And i Dont have any idea how to get the fastboot recognize my device....
Maybe someone have some time to help mi wlak through this 'issue' idiot friendly? I'm really confused and i dont have any idea what to do.
my hboot is 1.25.** JB. S-ON. I have installed TWRP recovery.
:crying: halp
EDIT:
SOLVED. Windows 7 FTW.
Also had this issue, quite frustrating as no drivers seemed to work for me, got if fixed now though (no need to go back down to win7)
Will_Xda said:
Also had this issue, quite frustrating as no drivers seemed to work for me, got if fixed now though (no need to go back down to win7)
Click to expand...
Click to collapse
So,what did you do ?:d
evnee said:
So,what did you do ?:d
Click to expand...
Click to collapse
Installed a HTC sync like program named PDAnet, and updated the drivers from that program, once in fastboot mode device is recognized in pdanet and in a command prompt (adb). this only worked on a usb2.0 port though.
(didn't bother replacing usb3.0 drivers as suggested elsewhere as this has caused big issues for me before.)
Guys I have already rooted my sgs3 and used many other roms. but few months earlier i put 4.3 stock rom to my device.
even now my phone is getting detected via odin(when it is turned on) and kies. But when i put it into the download mode phone isnt getting detected by odin. what i actually need to do it install custom recovery and root this device.
but now framaroot is not working and i have tried many other apks. please help me out
SLDarKprince said:
Guys I have already rooted my sgs3 and used many other roms. but few months earlier i put 4.3 stock rom to my device.
even now my phone is getting detected via odin(when it is turned on) and kies. But when i put it into the download mode phone isnt getting detected by odin. what i actually need to do it install custom recovery and root this device.
but now framaroot is not working and i have tried many other apks. please help me out
Click to expand...
Click to collapse
Aren't you just missing some drivers? Maybe try to reinstall them: http://forum.xda-developers.com/showthread.php?t=961956
Also make sure to allow drivers to interact with your device if anything prompts while in Odin.
Android Debugging activated?
blint6 said:
Aren't you just missing some drivers? Maybe try to reinstall them: http://forum.xda-developers.com/showthread.php?t=961956
Also make sure to allow drivers to interact with your device if anything prompts while in Odin.
Click to expand...
Click to collapse
Have you tried installing Sammy's USB driver?
And I'm presuming the device IS on download mode already (I don't believe it appears on Odin while on normal mode)
1. yes i have already installed drivers and phone is detecting via KIES and ODIN when it is turned on.. it suddenly disconnect whenever i put into download mode.
2. yep usb debugging is activated...
3. Im using 4.3 stock rom.. arent there any other way to root this device without pc .. coz i checked lot of forums but none helped me..
4. my pc - windows 10. but i dont think that it will be a issue coz it's detected when it's turned on (means not using download mode).
SLDarKprince said:
1. yes i have already installed drivers and phone is detecting via KIES and ODIN when it is turned on.. it suddenly disconnect whenever i put into download mode.
2. yep usb debugging is activated...
3. Im using 4.3 stock rom.. arent there any other way to root this device without pc .. coz i checked lot of forums but none helped me..
4. my pc - windows 10. but i dont think that it will be a issue coz it's detected when it's turned on (means not using download mode).
Click to expand...
Click to collapse
Bumping Up this thread since i have really same issue, as in literally the same.
Anyone can help me/us?
xaiury said:
Bumping Up this thread since i have really same issue, as in literally the same.
Anyone can help me/us?
Click to expand...
Click to collapse
mate you have to try a different PC or a port. I have fixed my issue using another PC
Download vroot PC Latest Version VRoot 1.7.8
http://www.vrootdownload.com
Downloading mode only..
I have tried 10000000000000000000000000000 tips tricks and almost everything in this and other websites.. but there is no solution for this:
I have GT-I9300 Pathetic galaxy SIII and since I tried flashing recovery to this it goes into download mode... and its been there ever since.. i have downloaded 32 different kind of drivers claiming Samsung drivers.., buying and trying 8 different USB Cables, formatted my laptop 3 time in order to get it detected by ODIN 3.04 to 3.12... or kies or Smart switch.. working on this piece of crap since 3 weeks day and night but getting nowhere,... If any one knows a way to get it fixed... EVEN IF IT NOT DETECTED BY ODIN OR KIES.
PLZ HELP....
Gr8mobiPro said:
I have tried 10000000000000000000000000000 tips tricks and almost everything in this and other websites.. but there is no solution for this:
I have GT-I9300 Pathetic galaxy SIII and since I tried flashing recovery to this it goes into download mode... and its been there ever since.. i have downloaded 32 different kind of drivers claiming Samsung drivers.., buying and trying 8 different USB Cables, formatted my laptop 3 time in order to get it detected by ODIN 3.04 to 3.12... or kies or Smart switch.. working on this piece of crap since 3 weeks day and night but getting nowhere,... If any one knows a way to get it fixed... EVEN IF IT NOT DETECTED BY ODIN OR KIES.
PLZ HELP....
Click to expand...
Click to collapse
Relax.. I understand how frustrating it can be.
I need a detail explanation of what you did to get it into that state and what you've tried. A bullet point list will suffice. I just need to know so I can work out how buggered it is and where to go from here.
I need to know which PC operating system you're using, which variant of s3 you have including its region (this can be determined by the sticker in the battery compartment unless you already know.
There is a possibility it is your os not detecting the device because of drivers but if you've tried formatting and starting over then it shouldn't have any issues. The only other option is to manually edit the drivers ".cat" file with the s3's actual physical address before installing the drivers, but this is in extreme circumstances when the os is not "playing ball".
Also remove kies or at least stop all of its running processes when using odin.
My advice at this stage is to manually remove all drivers from the pc OS regarding the s3 and wait until we figure out where the s3 is at. I have a gdrive with some useful stuff that I know works on Windows XP flawlessly. https://drive.google.com/folderview?id=0B4vTiHTBB629ZW5vQndpbjFnblk
One question though.. When you pull the battery out and reinsert it. Does the phone automatically boot to download mode, is it stuck there permanently or does it boot loop?.
Beamed in by telepathy.
shivadow said:
Relax.. I understand how frustrating it can be.
I need a detail explanation of what you did to get it into that state and what you've tried. A bullet point list will suffice. I just need to know so I can work out how buggered it is and where to go from here.
I need to know which PC operating system you're using, which variant of s3 you have including its region (this can be determined by the sticker in the battery compartment unless you already know.
There is a possibility it is your os not detecting the device because of drivers but if you've tried formatting and starting over then it shouldn't have any issues. The only other option is to manually edit the drivers ".cat" file with the s3's actual physical address before installing the drivers, but this is in extreme circumstances when the os is not "playing ball".
Also remove kies or at least stop all of its running processes when using odin.
My advice at this stage is to manually remove all drivers from the pc OS regarding the s3 and wait until we figure out where the s3 is at. I have a gdrive with some useful stuff that I know works on Windows XP flawlessly. https://drive.google.com/folderview?id=0B4vTiHTBB629ZW5vQndpbjFnblk
One question though.. When you pull the battery out and reinsert it. Does the phone automatically boot to download mode, is it stuck there permanently or does it boot loop?.
Beamed in by telepathy.
Click to expand...
Click to collapse
1st of all I want to thank you bro for reply...
Now..
I am using Windows 10 64bit, using Samsung galaxy sIII GT-I9300 Indian single sim varient.
I rooted it using KingoRoot successfully but I found I wasn't able to get SuperSU and without that I was not able to use root fun properly so I tried to flash the same with flashFire.. it failed as it require SuperSU. So I tried installing TWRP recovery from playstore and it started flashing and after reboot, It stuck on the Downloading mode.. No matter how many buttons I tried pushing combined it stuck on downloading mode...
I tried almost all method on YouTube and websites but it still don't work. Worst thing .. I tried fixing the same by Kies as well as ODIN but .. I never detect my phone.. when i connect my phone after uninstalling and Or installing the samsung driver and Kies as well.. windows didn't recognise it.
I am about to give up n this and almost ready to smash the phone with wall hammer and throw it under my car tyres but I committed myself not to do that before 14th May.
The problem is most likely Windows 10 64bit. I'm quite sure the drivers don't agree with them.
You're going to have to find an older OS and try it. Either use a virtual machine or dual boot and load up a real OS like XP. Then we can begin the proper problem solving. I hate putting percentages on things but I'm 90% confident that windows 10 is an issue here, mainly for the fact it is 64bit and the drivers aren't made for that.
As for button combo's if they don't work while booting and it goes straight to download mode then there is a big problem and it could be bricked. You can try holding just the power button for about 15 seconds while in download mode and it "should" attempt to reboot. If not then as I said, big issue ahead.
No matter what you need to get it seen by odin so get yourself xp somehow and use the stuff on my gdrive. You need to get yourself a copy of the latest firmware for your phone, ready to flash via odin should you get it to see the phone.
Beamed in by telepathy.
Windows 10 to win7
shivadow said:
The problem is most likely Windows 10 64bit. I'm quite sure the drivers don't agree with them.
You're going to have to find an older OS and try it. Either use a virtual machine or dual boot and load up a real OS like XP. Then we can begin the proper problem solving. I hate putting percentages on things but I'm 90% confident that windows 10 is an issue here, mainly for the fact it is 64bit and the drivers aren't made for that.
As for button combo's if they don't work while booting and it goes straight to download mode then there is a big problem and it could be bricked. You can try holding just the power button for about 15 seconds while in download mode and it "should" attempt to reboot. If not then as I said, big issue ahead.
No matter what you need to get it seen by odin so get yourself xp somehow and use the stuff on my gdrive. You need to get yourself a copy of the latest firmware for your phone, ready to flash via odin should you get it to see the phone.
Beamed in by telepathy.
Click to expand...
Click to collapse
I have moved to windows 10 to win7.. and tried all over again (in the process to downgrade the same i formatted by all drive.. thanks to my idiot brother)..
i tried all the same thing again but still no luck..
now trying windows XP 32 bit in virtual machine.
i will let you know..
and i am thinking to hand it over to samsung service center.. lets see what they can do?
Gr8mobiPro said:
I have moved to windows 10 to win7.. and tried all over again (in the process to downgrade the same i formatted by all drive.. thanks to my idiot brother)..
i tried all the same thing again but still no luck..
now trying windows XP 32 bit in virtual machine.
i will let you know..
and i am thinking to hand it over to samsung service center.. lets see what they can do?
Click to expand...
Click to collapse
If you can afford to have them look at it then it's up to you but you will be billed for it as the s3 is out of warranty. They haven't made the s3 for about 3 years now.
Beamed in by telepathy.
shivadow said:
If you can afford to have them look at it then it's up to you but you will be billed for it as the s3 is out of warranty. They haven't made the s3 for about 3 years now.
Beamed in by telepathy.
Click to expand...
Click to collapse
I know.. hopefully it will be done under my expectation.. or last thing I know to donate the same to hammer and trash bin :cyclops: