Posted this on the general discussion section but have had no replies, hopefully someone here can help?
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
have you try on a different pc?
maybe on your PC there is some problem with the drivers.
Moreover to connect via
adb u must enable Debug mode on your device in the application menu.
To flash kernel or other directly from your sd you can use the clockwordmode, but to install it you must before
install it and i fear you must use your cable connection
Sent from my GT-I9100 using XDA App
I have tried multiple PCs and a mac, even windows on bootcamp. I have installed drivers on every one, even uninstalled and reinstalled on one. One PC, my laptop was a fresh windows install (it was a linux box but I needed windows to use Odin). I was in debug mode and not in debug mode when attempting adb. Thanks for the suggestions though. As I said, I have tried numerous things and am completely stuck! so frustrating!
"I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device"
Exactly there... you can try to force device to install a different driver.
Double click the unknown device then driver then update driver then find software in your computer then choose manually from a list of device drivers in your computer then show all devices you should see "android adb interface" or something related to google or android.
Try it... i hope this can help you.
Related
i need help, i have tried everywhere and can't find anything and any help would be greatly appreciated
i'm on the road to root my samsung galaxy fascinate and have ran into a laundry list of problems. i have rooted many android phones coming from eclair, froyo, and gingerbread, but seem to be stuck at the slightest of problems when it comes to the fascinate.
i can not install the drivers to the fascinate. i have searched through the web for all the drivers and have tried every possible galaxy driver. the driver simply won't install on my windows 7 prof 64bit machine. i have never ran into this problem before with any other phone. every time i try to install the driver it gets to the very end of the install then pops up with the message "windows was unable to install the driver"
It also gave me the option to view the failed windows installation log, which after many successful steps, at the end the log shows this error:
Action ended 1:26:53: ShowMsiLog. Return value 0.
=== Logging stopped: 12/16/2011 1:26:53 ===
MSI (c) (0C:08) [01:26:53:750]: Product: SAMSUNG USB Driver for Mobile Phones -- Installation operation failed.
MSI (c) (0C:08) [01:26:53:750]: Windows Installer installed the product. Product Name: SAMSUNG USB Driver for Mobile Phones. Product Version: 1.3.550.0. Product Language: 1033. Manufacturer: SAMSUNG Electronics CO., LTD.. Installation success or error status: 1603.
i have also attached the entire log
the first thing i did was plug in the phone, which windows sensed this and automatically installed a driver, not sure which. after this i unplugged the phone and then checked "usb debugging" for rooting purposes and plugged the phone back into the computer which windows then installed another driver automatically, then following the steps from xda to root the phone, i downloaded the given drivers which is where the problem first occurred and the drivers were unable to download.
I'm simply trying to get root access to the phone and can't do anything with the phone with crappy drivers...i can't even mount usb sd card now to transfer data anymore. the drivers have completely been shot. i desperately need help. please
also what is the absolute easiest way to root the fascinate? is it with one click root or with Odin? Because the fascinate just updated itself from 2.2.2 EH05 to 2.3.5 EH03 and i'm not sure which program supports rooting which version of android. also all other android devices simply give root access to the stock rom, which is great cause i get to keep all my apps, messages, contacts...etc, then simply titanium backup everything and transfer it over to the new rom. is it different with the fascinate? will rooting the device simply flash a completely new rooted rom? therefore loosing everything? if anybody has any answers to any of these questions, please be my hero. thanks
Uninstall everything you previously installed in the way of Samsung drivers (in fact, you could use Windows 7 backup and restore to restore your PC to the state it was in the day before you installed the drivers as they are sometimes hard to uninstall completely). Reboot and simply plug your phone (with USB debugging of course), and let Windows automatically install the drivers for you like it did before you installed the ones linked to on XDA. This time, if your PC recognizes your phone, just keep the drivers you have and don't install the ones linked to. Those drivers from the guide are for those whose PC doesn't automatically install working drivers. From that point, just follow the rest of the guide and skip the install drivers part. You will not have to install any further drivers unless you flash an AOSP ROM, in which case you'll have to follow the instructions in the OP of the ROM thread. I hope this works for you.
Has anyone seen John Connor?
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
bigwhat said:
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
Click to expand...
Click to collapse
root is not flashed via odin, rather cwm is...then the root file su_2.6.3.1 is flashed via cwm. If you need directions section 5 of my guide in general section has it covered...everything needed is there including the correct recovery and root file.
I will tell you what...the Fascinate is probably the biggest pain in the ass phone...I tried forever to root my friends and couldn't get it done...need to try again I guess, but it was a driver issue as well..ODIN just wouldn't recognize the dam phone
Use Droidstyles guide. Very easy to follow. Also, the USB cable for some reason seams to be a bit finicky at times with this device. Unplug from phone and replug. Sounds odd but trust me, I have done this many times.
Sent from my SCH-I500 using XDA App
I am having a problem too and it's not covered anywhere i've seen to date. I've got an XP and a Win7 box at home. On both, I've tried with no drivers and i've tried with every other driver set I can find and every time I hook the phone up to the machine it pops up saying USB device couldn't be recognized or something. I'm going nuts! I've never had so much difficulty in my life, not even the first time changing ROMs on anything.
Droidstyle- I've seen your guide and unless I missed it doesn't cover this. Have you seen or heard of this and have any ideas at all?
Thanks!
People!, I'm about to pull all my hair out on this one
Vibrant is soft bricked in a boot loop after a incomplete flash, I am able to get it into download mode but both my windows machines say USB device isnot recognized, and thus, I cant use ODIN to return to stock. When I try to manually point windows to the samsung drivers I get nothing…
So far I have tried drivers from:
-Bay_wolf's AIO Vibrant Toolbox 2.5
-USB drivers for vibrant from samsung support site
-Drivers from samsung keyes
Side notes that might help: I was perviously using a Hellybean Rom. My device displays "Galaxy S gt-9000" on boot... not sure when that came to be but maybe some rom changed some important recognition stuff??...
I found this thread http://forum.xda-developers.com/showthread.php?t=1008383 but no help...
Any help would be greatly appreciated!!
Try a different USB cable. This happens more than you'd think. Even cables that have worked just fine hundreds of times.
Also.... Locate the drivers in system/device manager and delete them manually and try to install them again. Unplug device and install fresh ones from either aio toolbox or Kies, then plug phone back in.
Best of luck!
Toast6977 said:
Try a different USB cable. This happens more than you'd think. Even cables that have worked just fine hundreds of times.
Also.... Locate the drivers in system/device manager and delete them manually and try to install them again. Unplug device and install fresh ones from either aio toolbox or Kies, then plug phone back in.
Best of luck!
Click to expand...
Click to collapse
Thanks a ton for reply but, sadly, no dice.
Tried connecting the phone, getting the "unrecognized device" prompt, finding "unknown device" in device manager, right clicking to uninstall. rebooting my machine, using various install methods to re-install drivers, re-connecting, and nothing.. same issue...
I lost the original cable a while back, but can't accept that NONE of the other 5 cables used are all broke... specially if the computer recognizes something going on... is it worth buying a new one?
Losing hope here, been like this for 4 days now, think it's time to go get a new phone. :crying:
Even so, it would have been nice to get what was a perfectly working phone back if only to keep it as a mp3 payer.
If anybody in New York, NY has a working odin set up that can do this for me, I have a 6 pack of your favorite beer with your name on it.
It could be a hardbrick such as bootloader getting corrupted that happened to my Sony Xperia Play (now an expensive paper weight).
I assume you boot into download mode by holding the two volume buttons, then connect the cable? Have you tried on a different PC? It can also be the weak powered USB port on the PC. Also when you uninstall the Samsung driver, check the option to also delete USB driver and uninstall any drivers. Also which version of the driver are you using, have you tried version Samsung USB Driver 1.5.3? And the drivers from here: http://www.samsung.com/us/support/owners/product/SGH-T959ZKATMB#
For what its worth, the gt i9000 screen appears after your on a custom GB boot loader and Odin back to stock (or probably Odin flashing any other ROM) you can change it by flashing the GB boot loader again. My phone says its a i9000 too, but I'm just about lazy enough to not bother changing it, lol.
So that's unrelated.
eksasol said:
It could be a hardbrick such as bootloader getting corrupted that happened to my Sony Xperia Play (now an expensive paper weight).
I assume you boot into download mode by holding the two volume buttons, then connect the cable? Have you tried on a different PC? It can also be the weak powered USB port on the PC. Also when you uninstall the Samsung driver, check the option to also delete USB driver and uninstall any drivers. Also which version of the driver are you using, have you tried version Samsung USB Driver 1.5.3? And the drivers from here: http://www.samsung.com/us/support/owners/product/SGH-T959ZKATMB#
Click to expand...
Click to collapse
Ok, faith momentarily restored. But I have questions:
-What do you mean when you say "check the option to also delete USB driver and uninstall any drivers"? I dont get such a prompt from right clicking on "unknown device" and selecting uninstall? Is there another method to uninstalling drivers?
-In the link attached, I can only find "Device(Install),USB Driver (Software) (ver.1.0)" not the 1.5.3 version mentioned. What am i doing wrong here? currently searching google for the 1.5.3 but finding nothing.
I get into download mode by holding volume- up + power. Have 2 PCs ( win xp and win 7) and a mac running mountain lion (but never ever have been able to get Heimdall to work, so devoting time to odin.)
Thank you for the time + help, guys, I really do appreciate it in the time of utter un-nerdness.
If the device is already installed it will have a check box that said "Delete the driver software for this device." If its unknown then obviously not. By "uninstall any driver", I mean uninstall any Android drivers you current have installed and reboot before you reinstall the new driver.
Although I doubt it will make a difference than the one I linked above, you can try the Samsung driver version 1.5.3: http://www.mediafire.com/?r0uc3h413qcy80z
If you did manage to get into download mode and see this: http://images.google.com/search?num=10&hl=en&site=&tbm=isch&source=hp&q=download+mode
Then it mean there is a very good chance you can restore the phone, if you can find a computer to recognize it and Odin to see a COM port.
I definitely think it would be worth the money to go buy an OEM USB cord. I can't tell you how many times I have seen this and a new USB is the fix.
sent from the depths of helly bean
OK guys...
My friend, who also owns a Vibrant, let me borrow the cable that came with the phone for the last 2 days.
Tried to make ODIN work on both PCs at home, gave Heimdall a shot on my mac, even hijacked a computer at work for the better part of the morning and freshly installed USB drivers 1.5.3 before connecting. All for nothing... “Unknown device” across the board....
At first I felt that with being able to get into download and have SOME kind of a reaction from connecting to PC had to be a good sign. Almost completely convinced that there is some unknown, unworkable hardware problem present. Definitely, officially, unremarkably out of ideas here.
Nothing is beautiful and everything hurts.
Last thoughts? Options at this point?
Also, tried One-click Unbrick tool on mac. I got a "is your phone plugged in, is it on download mode?" error, but anyone reading this down the line with a similar problem should check it out.
http://forum.xda-developers.com/showthread.php?p=15330252
Hi all. So I just picked up a Verizon Note 2 today and happily looked forward to rooting it. I'm on 4.1.2 Jellybean VRAMC3, model number SCH-I605. I'm afraid I may have messed something up.
I had downloaded Odin and installed the Samsung USB drivers and all that good stuff. Odin picked up the phone and all that, but a bit more looking around seemed to indicate that the usual Odin method of rooting wouldn't work on the latest version that I had.
So I downloaded the CASUAL installer and got that to run. It ran through the install, rebooted the phone, and then said it was waiting for Windows to recognize the device again so that it could continue with the install.
At that point, Windows informed me that a driver install had failed and the CASUAL install did not proceed any further, despite waiting a good 5-10 minutes.
Since doing this, the phone has had bizarre USB connection issues. Odin and Kies do not read the phone at all. Plugging the phone in brings up an additional drive for about two minutes with a Verizon Assistant Manager EXE, a USB Drivers EXE, and a couple other things, then it disappears.
The phone will often display a message informing me "Unable to find software on your PC that can recognize your device." This happens regardless of being in USB Debugging mode or not.
I've tried uninstalling and reinstalling several versions of Samsung's drivers as well as Kies. I also tried a factory reset on the phone itself, but these connectivity issues (and accompanying warning messages) persist.
Not sure how to proceed from here and would love a bit of help. Thanks!
Additional notes: All normal functions of the phone are working fine, and the computer DOES detect the phone as a "Samsung Android Device", but as stated Odin and Kies are not able to detect/connect with it.
Update: Messed with drivers a bit more and Odin will now pick up the phone again. When the phone disappears as a "drive" with install helper stuff, it reappears as a portable device, and I can browse the innards of the phone to put music and other stuff on it. CASUAL however still does not pick up the phone.
So after flashing 10/17/15 release of Tesla Arc_Flash I am unable to connect to the phone through adb without deleting the driver and adding it as an adb device. I have installed the LG G3 Verizon drivers but I am still not able to connect. In the device manager it shows that the drivers aren't there but also that they are there as a portable device. hxxp://tinypic.com/r/30ua82f/8
Also the command prompt is below. Brand new adb server started.
hxxp://tinypic.com/r/71myr4/8
Any help would be appreciated. If you need logs or anything else I am happy to provide it. Also since I feel this may get asked... Yes I have USB Debugging turned on. Have tried with Root for adb on and off and nothing seems to work. I can get it to connect through network but I don't want to constantly have to look for the IP address and port. This was also an issue in the previous release of Arc_Flash so please let me know.
Hi! Exactly what drive did you install and where did you get it from? Here is where I get the driver from http://www.lg.com/us/support-mobile/lg-LGVS985. Try rebooting the PC (without the phone connected) after installing the driver. Using the original cable that came with it, connect the phone to a different USB 2.0 port than you had tried previously - it can take up to 10 minutes to finish loading the driver. When it's complete Device Manager should have a listing for the phone in the Modem section, which isn't currently listed in your screenshot. Until you can get that solved you won't be able to reach it with adb.
Have you searched the Tesla ROM thread to see if anyone else has had the issue, in case it's specific to Tesla?
roirraW "edor" ehT said:
Hi! Exactly what drive did you install and where did you get it from? Here is where I get the driver from. Try rebooting the PC (without the phone connected) after installing the driver. Using the original cable that came with it, connect the phone to a different USB 2.0 port than you had tried previously - it can take up to 10 minutes to finish loading the driver. When it's complete Device Manager should have a listing for the phone in the Modem section, which isn't currently listed in your screenshot. Until you can get that solved you won't be able to reach it with adb.
Have you searched the Tesla ROM thread to see if anyone else has had the issue, in case it's specific to Tesla?
Click to expand...
Click to collapse
I searched the ROM thread but found nothing matching what I am experiencing but I followed everything even close to it. I installed those drivers just now and restarted both computer and phone. Still comes up as an unknown driver. There is no modem section inside of the computer still. I can manually add the drivers but it still doesn't seem to help.
Also to add. I also have tried to add it as a modem and it gives Windows Error code (10) that it can not start the driver. I forgot to mention. Windows 10.
Well, I've connected to my phone via adb and used the LG flash tools on Windows 10 last week or the week before, although I have my insider updates set to Fast Ring and I kinda regret it because there was a recent huge push of a beta Windows, and they've broken how I had my video associations set up and I can't get my subtitles to work any more either. Sorry for off topic. My point is since Windows 10 is considered a constant "change in progress", and especially for people like me who joined to get "insider" builds, it's hard to tell what makes things not work. My main reason for even being on Windows 10 is to see what they come up with in their insider builds, but I guess when it mucks with my video enjoying ability, I start losing my patience.
I would seriously consider trying a different PC, or if you have the capability of performing a fresh Windows installation, even of Windows 10, that very possibly would fix it. Or if you just recently, within the last 30 days, upgraded from an earlier Windows to Windows 10, and didn't perform a clean installation, you can revert the upgrade through the the Windows settings. No idea if reverting would solve the problem, either, though.
As @bweN diorD pointed out in another similar thread just yesterday or the day before, when someone in your situation ends up trying a different PC, then everything goes smoothly. As far as the cause, there's too many variables.
If you can't use anyone else's PC, there's an outside chance that you could even do it at a library computer, as long as you don't reboot the PC (which I usually recommend after initially installing the driver, but sometimes things work fine without that). Rebooting a library PC usually undoes all changes, putting it back exactly the way it was.
Let us know how you make out.
Okay so I've ruled out a couple of the culprits and I still struggle to connect my phone
The Cable,I know this because I've tried the same cable on a different phone and it work perfectly
The MTP drivers,I know this because I've installed this more than twice and restarted both device more than I can remember also every single driver I have installed gives me code 10 error and doesn't work after restart.
all of this happened after I tried to flash twrp on my device and when I pressed flash on the SPflash app it didn't flinch so I restart my phone, and lo and behold it starts to transfer files from the twrp .img file and after that my phone was still connected but nothing changed twrp wasn't there, but my phone was still connected and I when I progressed through the page on how to flash there was the drivers for it MTK drivers after I installed them nothing was working, so I uninstalled the phones drivers, exactly after that my phone wouldn't connect again, like I said I tried every thing, that I could do.
All I wanted to do is to root that old phone and give it a new life but no something has to go wrong and I tried going to the manufacturer's website for the drivers but no dice, I tried posting on the manufacturer's forum and still nothing they haven't even replied to my post about it being publicly available, so I hope that someone out there can help me diagnose ans fix this problem.
I'm on android 8
its a blackview bv8000 pro