Hi everybody! First post here so please forgive me if I step over any bounds. I have a Verizon Samsung Galaxy S III (SCH-I535 is the model I believe?), OS version 4.1.2 and I'm having some problems rooting/unlocking it. My goal is to use it on the ATT&T network, which I've seen has mixed success when I researched it, but I'm currently rocking an iPhone 3GS so it doesn't get much worse. When I plug the phone into my computer (and I've tested it on a few now), it immediately begins charging, says it's connected as an installer, and by all accounts seems to be fine. On my computer though, a notification bubble pops up and says 'USB Device not recognized' (see pics). I've tried manually installing the drivers for the 'Unknown Device' in the Device Manager, uninstalling the Samsung drivers and installing a slightly older version, bending the tongue in the USB port slightly upwards, blowing in the port, connecting it as PTP and MTP (all solutions I found online), still to no avail. One thing I wanted to try but was unable to is plugging the phone in while it's in download mode. I can restart the phone into Download mode, but at the prompt I can only press the down arrow because the volume up button on the rocker is broken! None of the reboot apps on the Play Store would work for me. So, my question are:
1.) Are there any other solutions that might help me get my computer to recognize my phone so I can root/flash it?
2.) Is there any other way to enter recovery mode or bypass the prompt on an unrooted phone? Thanks a bunch for the help everyone!
P.S. I'm running Windows 7 SP1, and I recently rooted my friend's Note 2 successfully using the computer and cable so I don't think that's the problem.
Wrong forum, this is for the i9300 only.
Related
Firstly I apologise if this has been covered anywhere - I read a load of posts and did a load of searches but came up empty handed about this specific issue.
I bought a Galaxy Ace (GT-S5830 Baseband:S5830NEKA3 OS:2.2.1) as a dev device and it's been working fine up until today, and at some point it decided it doesn't want to be able to connect to my computers. I've tried three different computers, two different operating systems, and ever tried installing Kies (urk) with no luck.
The phone can charge over USB, saying that it's charging over AC, but that's all that happens.
I can't boot in to recovery mode as holding the power+middle button+vol up just gives me a ramdump message.
Can anyone help me out?
Martyn.h said:
Firstly I apologise if this has been covered anywhere - I read a load of posts and did a load of searches but came up empty handed about this specific issue.
I bought a Galaxy Ace (GT-S5830 Baseband:S5830NEKA3 OS:2.2.1) as a dev device and it's been working fine up until today, and at some point it decided it doesn't want to be able to connect to my computers. I've tried three different computers, two different operating systems, and ever tried installing Kies (urk) with no luck.
The phone can charge over USB, saying that it's charging over AC, but that's all that happens.
I can't boot in to recovery mode as holding the power+middle button+vol up just gives me a ramdump message.
Can anyone help me out?
Click to expand...
Click to collapse
When phone is turned off. Press and hold home+power/lock button untill it reaches recovery menu.
Check - that works. Thanks.
I'm now unsure as to how to proceed - neither adb devices nor fastboot devices are reporting anything back.
Connect device to pc. Open device manager (windows). Remove all drivers related to the ace and Samsung.
Remove the device and reboot the pc. Then connect the device. Windows update will detect the device and install the necessary drivers. If it doesn't automatically do that then open up device manager and install them manually by right clicking on the device and selecting update drivers from internet.
From the Galaxies to your Ace...!!
Thanks for your reply.
In windows there's no sign of any Samsung or Galaxy Ace drivers. Plugging it in to my Kubuntu machine gives me identical lsusb results as when not plugged in.
Have done a data wipe, checked that USB debugging is on and tried different cables
think it's screwed.
Think I could stick a ROM on the SD card and flash it? Would that work?
Martyn.h said:
Thanks for your reply.
In windows there's no sign of any Samsung or Galaxy Ace drivers. Plugging it in to my Kubuntu machine gives me identical lsusb results as when not plugged in.
Have done a data wipe, checked that USB debugging is on and tried different cables
think it's screwed.
Think I could stick a ROM on the SD card and flash it? Would that work?
Click to expand...
Click to collapse
hmm.. kies didnt work right? So i guess only option IMO would be card reader or CWM
Yep , the phone's USB port is frayed
This was sent from a Galaxy Ace. Problem?
Hi, first post here.. so Hi
I have an issue with my S3, i can't get my pc to detect it in download mode at all, no reaction from windows.. if didnt plug it in to the pc at all, it worked once, and it took me reinstalling drivers for hours to get it working, this is when i first rooted the phone using the cf-root method..
When i wanted to install a custom rom a few months ago i discovered it went back to not getting detected and has stayed that way
it's as if i've not connected it to the pc at all, i'm using a rear usb port, with the original cable, below is a short list of what i've tried
Tried 3 different cables
Used a brand new install of windows 7 with SP1
tried various Samsung ADB Drivers
Tried every single USB port, front and back on my pc
Used as many different USB Debugging options as possible
I noticed that when i turn on USB debugging after enabling developer mode, nothing changes on the pc, if i remember rightly my S2 made windows install the adb driver when i turned USB debugging on..
Any help is appreciated with this, never had any of this happen with my S2 lol :/ i've been messing around on and off the last few months with it, thankfully there's Mobile Odin and also Nandroid backups for me to fall back on
Pulling the battery with the cable plugged in while my S3 was in download mode is what fixed this for me...
With the usb cable plugged into the PC but NOT the phone, go into download mode.
Connect cable to the phone, then pull the battery out.
Once windows detects the phone and installs drivers it's safe to put the battery back in.
Phone will be detected by Odin/ CyanogenMod installer and so on.
Why in hell having the battery in stops windows detecting the phone in download mode is beyond me.. unless samsung did it on purpose? lol..
Installed CM 11 using the above method and it went perfectly, but i do have to use the above method whenever i want to flash something using my pc, so it's more of a work around than a fix..
Fix was found on YouTube of all places! hope this helps anyone else
Hello All,
I've been reading posts from here for a long time but this is my first post.
I'm coming here as a last resort to save my Galaxy s2 (SGH-T989) which has a stock ROM.
Here's what happened.
I dropped my phone and then it got stuck in bootloop (it only boots until I see the "SAMSUNG" word animation and stops there).
At that point, ODIN 'sees' that there's a connected device; KIES keeps "connecting...." but can't actually connect; ADB does not show any connected device.
So, what I wanted to do was to factory "reset" the phone. The problem is I can't get the phone into Recovery mode. I believe it's because my volume down button was acting up when the phone was working. However, I can get to "Download Mode" using a USB Jig.
So, the next thing to do is to flash a new stock ROM. However, whenever I connect my phone when it's in "Download Mode", ODIN does not see it.
Yes, I've installed, re-installed, removed, re-installed all drivers and Kies and I've done that so many times you can't even believe it.
The problem is that the device driver "SAMSUNG Mobile USB CDC Composite Device" gives the following error "This device cannot start. (Code 10)", and I don't know why or how I can get rid of that. As mentioned above, I've tried all the device driver installation fixes but none has worked.
I mean, when the phone is not in Download Mode and I connect it to my PC, all device drivers are working fine with no error, but when it's in Download Mode, I get the error mentioned above "This Device cannot start.".
So, my questions:
1) Is there a way to get to Recovery Mode without using the button combinations? (The phone is in bootloop)
2) How can I fix the device driver error mentioned above to get ODIN to see my device?
3) Is there anything else I need to be doing?
This problem is really frustrating and I've been on it for more than 2 weeks and nothing has worked so far. Any help is greatly appreciated.
1. I think you have flashed an bad kernel if you cant get into recovery mode and i dont get it why your volume down acts like up?.
2. http://support.microsoft.com/kb/943104 try to maybe also disable kies and try again.
3. Kies is on, adb doesnt work at samsung/download screen, try to reinstall samsung usb drivers again :/ yes I know but to be sure, disable driver signature or something like that if you are on windows 8.x, try another usb cable.
2weeks dont sound good. I hope these tips could help a bit but I still wonder why your phone got in bootloop when you dropped it !?!? What were you doing at that time and did the battery go out?
wulsic said:
1. I think you have flashed an bad kernel if you cant get into recovery mode and i dont get it why your volume down acts like up?.
2. try to maybe also disable kies and try again.
3. Kies is on, adb doesnt work at samsung/download screen, try to reinstall samsung usb drivers again :/ yes I know but to be sure, disable driver signature or something like that if you are on windows 8.x, try another usb cable.
2weeks dont sound good. I hope these tips could help a bit but I still wonder why your phone got in bootloop when you dropped it !?!? What were you doing at that time and did the battery go out?
Click to expand...
Click to collapse
Thanks for the quick reply, wulsic.
1. No, I did not flash any kernel on this phone, everything on it is stock and was working just fine before it was dropped. I meant that the volume down was not working properly, not that it was acting like up.
2. I tried that but did not work
3. The drivers are working fine when the phone is not in Download Mode, it's only when it's in Download Mode that I get the error and I've tried re-installing drivers and everything, I think the problem is with the device itself not a driver problem.
I originally posted a threat up on reddit, but I couldn't find a fix for it.
I got a Note 2 do Android development on. I for the life of me cannot get the damn phone to connect to any PC I connect it to via USB; the phone charges, just does not connect. The USB icon does not appear on the device when connected either. I tried 3 different Windows machines, with the same warning I get that the device isn't recognized, but reads it as an 'Unrecognized Device'. I have also tried OS X, does not read it as well.
Here is some of the things I've tried from reading around XDA and other forums that haven't worked for me.
Solutions i've tried with no fix:
Various USB 2.0 cables (I do not have the original cable)
USB 2.0/3.0 and other ports repeatedly.
Enabling USB Debugging
Installing Kies, and Samsung driver from their site
Resetting battery
Booting into recovery mode with device connected
Dial codes for some reason do not work on my phone. I tried entering them with the stock dialer to bring the USB settings, but they don't work. I got around it by installing an app to get the USB mode to MTP, still does not work.
Rooting right now is not option, since Odin requires to be mounted to a machine in order to root. So I'm pretty much stuck. Still can't get this phone to sync on anything.
Device info
Model: SCH-I605
Carrier: Verizon
Android version: 4.4.2 (Kit-Kat)
Stock ROM/Non-Rooted
I've been flashing custom roms on android devices for several years, but the Gtab S3 is the first Samsung device I've ever dealt with. On top of that I normally use ubuntu and I'm not familiar with window. I'd be most appreciative for your help with odin:
1) When I first plugged the S3 into a window machine I thought it would complain about lack of usb driver. It does not, to my surprise (it seems unlikely that that laptop would have the drivers already installed but maybe I was wrong); nothing happens on the Window side, and S3 says that it's getting slow charging.
In any case I installed the OEM usb driver in https://www.xda-developers.com/where-to-download-android-usb-drivers/ and then plug in the S3, but again nothing happens.
2) I installed odin 3.12.7 but it does not seem to see my S3 (see the attached screenshot).
3) The OP of this thread says
"put your device in download mode"
How?
I did try to google around but I have not been able to find useful help (e.g. as the screenshot shows my odin does not look like the one in step 6 of www.techbeasts.com/how-to-install-twrp-recovery-using-odin/). I enable USB debuggin mode & OEM unlock.
Many thanks for your generous help.
Maybe I cam help.
First have odin up on your pc with the usb cable plugged into the pc but not the tab.
Then with the tab turned off simultaneously hold the power, vol down, and home buttons. The tab should boot into download mode. Hit vol up to get into download.
Now plug the usb cable into the tab.
You should see odin recognize your device and then be able to flash.
You need the Samsung USB drivers and DOWNLOAD mode.
http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
.