So I Odin'ed back to stock today with the intention of flashing Bionix 1.2.1 and it went off without issue. Then, when I went to connect it to my laptop it of course asked me what kind of connection to use and of course I chose Kies. That's when it all went downhill. The Kies screen would flash back and forth from my home screen over and over in an endless loop. I scratched my head and decided to try doing it via mass storage and my computer does not recognize it. I tried reinstalling the usb drivers but that did not solve any of my issues. I tried to re-Odin which didn't solve the problem either.
So I am at a loss, I had a similar issue before where I'd connect through Kies and my laptop would tell me my phone is no longer responding/stopped working but I was still able to connect via mass storage. So I am at a total loss and I am hoping someone here can help me resolve this issue. Thank you for reading.
[Edit]: FIXED.
Related
I am a proud new owner of shiny new Galaxy S Vibrant. I was working on new wallpaper, and trying to resolve the issue of why my custom 960x800 wallpaper was not as sharp on my phone as it is on my desktop. That was yesterday, so today I thought I'd give it another go, but now for whatever reason, my phone wont' connect to my PC. I am running Windows 7 32Bit. I have seen all the issues others have had connecting to their PC. I have tried all suggestions from those other threads, and none work. But here's what really annoys me, each time I attempt to connect my phone to my PC I get various responses from my PC. Sometimes the PC says "installing drivers," but it fails to do so, other times in the upper right corner of the Kies window it will say "connecting device" but never does. Some times the mtp application screen on the phone flashes as it attempt to connect, other times it doesn't flash, but still say its attempting to connect. I was able to connect once today. But after disconnecting, it has gone back to not wanting to connect. I'm not even trying to connect to Kies anymore, the phone won't even get recognized as a mass storage device. I tried the phone on different USB Settings (ie. Ask On Connection, Samsung Kies, Mass Storage, etc...), also tried unmounting and mounting internal SD card (don't have external sd card) and still no success. I tried uninstalling and reinstalling drivers, and rebooted PC and phone. I did the dreaded formating of the internal sd card and Even rebooted my patience, but still get no love between phone and PC. I think it's juast a matter of bad bad bad Drivers, not the Kies software itself. The driver is what makes the device and PC comunicate. I think Kies itself is ok. In a world of plug in play, what a way to put a damper on a completely otherwise beautiful mobile phone experience.
ive had some problems with kies but its always when ive flashed new firmware and my only solution was to uninstall kies then reinstall.
i dont think it should be called kies cos kies open doors and let u enter while this kies shuts the door and wont let you fooking in.
regards
Help, I have a weird problem with my phone. It keeps saying it's "connected" to a usb cable when it's not. Can still get it working fine and everything but the major problem is when I "power off" the phone. I cannot turn it back on unless it's connected to a usb cable.
This happened on last night, I'm thinking it's a hardware issue and may need to be replaced but was wondering is there anything else I can do?
I've tried hard reset the phone (that is it formats EVERYTHING on the phone, done through the service code). Tried factory reset, didn't work.
Tried flashing a new firmware with repartition, didn't work either
Can anyone help or suggest what I can do?
Thanks.
If I return this, might get another phone. since the gps is **** on this anyway
I have done searching with my crappy searching skills and cannot find anything that has helped yet so here is my problem.
I have my buddy's phone that was rooted but never given cwm and so is running the stock rom. The phone itself will not go into debug mode when I plug it into a computer. I have reset the phone through recovery and in the os but neither have fixed the problem. Is there an update zip i can flash to fix this? Or what do I do?
I'm running Win 7 32 and have the samsung drivers installed.
Figured it out, the phone has a bad connector.
Okay. Hi guys.
I'm having some horrible USB connection problems and I've no idea whether they are hardware/software. I'm leaning towards the former.
About a month ago I noticed while plugged into my charger, my phone wasn't charging. Wiggling the cable did little, if anything to help. But it only happened that one day, and after a few beeps and boops of connections coming and going, it had seemed to have fixed itself.
Yesterday I decided to upgrade from XtreStoLite KitKat to XtreStoLite Lollipop. I made a bit of a mess of it and accidentally wiped my entire OS/cache/data before even putting the ROM on the sdcard directory. Fortunately I had already upgraded the modem/bootloader and was able to sideload the ROM.
I say I was able to sideload the ROM successfully, but this is really where the issues started to resurface. The first dozen or so times I tried to sideload I got "ADB not recognized" errors in CMD. I tried all sorts of USB driver re-installations, and installing google USB drivers from the Android SDK etc and nothing was working. Lots of beeps and boops of drivers installing and USB connections being made. In a last ditch attempt, I went back to CMD and once again typed "sideload adb rom.exe" and by some random miracle it worked. But that was the LAST time. I tried again later and got the same error as previously.
Anyway... new ROM installed. I ran through the set-up process and plugged my phone in to transfer over the add-on pack so I could re-activate Samsung Kies connections in order to restore my apps/photos etc.
*B-beep-b-b-b-eep-boop-b-beep* The phone was wildly connecting and disconnecting. I unplug it, blow into the USB connector - try to see any bent pins, but can't see anything. After a few tries I get it to connect long enough for me to transfer the file. Kies reinstalled. Throughout this WHOLE process there has been FAR too many disconnects.
If I DO get my phone to connect - Kies is stuck eternally on "connecting". I have a feeling MTP mode is just broken - as NOTHING shows up in My Computer when in that mode. Odin 3.09 no longer sees my phone at all, and when I connect in Camera mode NONE of the .zip files I placed in the sdcard directory show in Windows at all. But they ARE there, as I can still install from .zip in recovery.
The phone seems to work fine. But I want to restore my Kies backup, add/remove the .zips in the main sdcard directory, and see my phone in Odin.
Please help me. I am scared.
Received a replacement device yesterday that is NG2. No big deal as I CF-Rooted it, then placed TWRP on it. Did a backup of initial state and went to transfer a rom to SD card and realized the phone would not connect
to PC as a device. Now I have 2 other S4's in the house and they connect immediately so it is not a driver issue with the computer(Win8.1), or USB cable. The 2 other S4's immediately are recognized by the computer.... I
have found that this one is recognized only while in Download mode, but when booted, nothing. I reinstalled the backup I first created and did a wipe 3x and I was able to get it to go into USB mode only 1x. The USB
icon appeared in the upper left of the screen and Kies recognized the device for the first time. After that I thought I was good so I went to the CF-Root installed Superuser app and opened it. It prompted about knox so
I ran it for knox disable. Bam, no more USB. What is going on here? I have rooted and worked with 5 or 6 different S4's with no issues. This is my first at NG2, and I want to point out that it is not activated yet as well.
Does not completing the activation trigger something? I am just trying to figure out if I should just return and swap for another. I have tried to reflash back to stock and wipe and it no longer offers the USB connection I
was able to achieve at the 1 point. This is an odd one and again, it is NOT drivers or the USB cable.....
Thanks,
Lisnup65
Fixed. Returned the phone for another one.