My younger brothers phone, a Samsung Galaxy SII GT-19100T is stuck at the screen "Samsung Galaxy SII GT-19100T" so I went into his recovery setting. For whatever reason (his phone was hot, so I imagine something was running and caused this just a short while prior, it was charging, so I don't know what he could have done, he refuses to tell me if he infact did do anything) it states that there was a failure to mount /data, /system , /cache etc, so I attempted to restock the original firmware on Odin. I had done this Last year on his phone, it worked fine. However, this time, it fails, and at times, says something about a Failed COM port, of which I have no understanding. I do infact have Kies installed. However, I have attempted to update the drivers, if that was the fault, nothing. I had done it also with both Kies open and Kies Closed. I really need help here
twinsniper said:
My younger brothers phone, a Samsung Galaxy SII GT-19100T is stuck at the screen "Samsung Galaxy SII GT-19100T" so I went into his recovery setting. For whatever reason (his phone was hot, so I imagine something was running and caused this just a short while prior, it was charging, so I don't know what he could have done, he refuses to tell me if he infact did do anything) it states that there was a failure to mount /data, /system , /cache etc, so I attempted to restock the original firmware on Odin. I had done this Last year on his phone, it worked fine. However, this time, it fails, and at times, says something about a Failed COM port, of which I have no understanding. I do infact have Kies installed. However, I have attempted to update the drivers, if that was the fault, nothing. I had done it also with both Kies open and Kies Closed. I really need help here
Click to expand...
Click to collapse
Just remove Kies, install the drivers again, and then boot to download mode to restore, as your problem says "Failed COM Port", and it is related to drivers.
Another workaround: if you have another PC nearby, try doing the above mentioned on that PC. Just don't install Kies at all.
Regards.
Related
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.
Hi guys, I need some help with my Samsung Galaxy S3 GT-I9300.
A couple weeks ago my phone turned off by itself and never turned on completely again. If I turn it on, it stays on the very first boot screen forever (the white text saying Samsung Galaxy S3 GT-I9300, like this one (https://cdn-images.xda-developers.com/direct/1/1/5/2/1/9/8/I9300.bootlogo.jpg).
I've removed the SIM card and the MicroSD card with no effects whatsoever, and I've also left the device turned on for hours but it always stays on the same screen.
I cannot enter recovery mode (it just shows the boot screen mentioned above) but I can enter download mode. At download mode, I get this info:
ODIN MODE
Product name: GT-I9300
Custom binary download: No
Current binary: Samsung Official
System Status: Oficial
As you can see, I have never flashed a custom rom (or rooted or even unlocked the bootloader). This is what intrigues me the most, since everybody I've seen with the same problem had trouble during or after a flash.
My last OS version was 4.3.1 and it was received OTA months ago.
In the past few months, my device rebooted out of nowhere, even when I was not using it. Occasionally, it had the stuck power button, which caused it to reboot on a loop, but I always solved it by nudging the power button a little. I don't know if these two previous problems might have caused the problem I'm facing now, but they're not showing up anymore.
Anyway, I've tried to flash the newest official rom (NK1 - ZTO) via Odin but I always get a NAND Write error.
I've tried changing USB ports, USB cable and computers; tried Odin 3.04, 3.07 and 3.09; tried Samsung USB drivers v1.5.45 and 1.5.49 but nothing of the above made any difference.
Today things started getting worse, though. In the past, Windows would always recognize the device on at least one specific USB port; Odin would also recognize the device and then I would get the NAND Write error. Now, Windows will not recognize the device no matter the cable, USB port or driver version. I only get a unknown device error and Odin won't recognize anything connected.
I tested all my setup with a working Galaxy S3 I9300 and it got recognized every single time, no matter the USB port, the cable or the computer.
Considering that another device is getting recognized by different computers, I suppose that the problem lies in my Galaxy S3.
So, can anyone offer me any kind of advice or point me in any direction on how I can try to fix my phone? Is my phone physically dying and no software solution will unbrick it?
Your power button issue has corrupted/damaged the nand memory. Try the dead boot recovery thread in general forum but unless you have warranty you might be better off with a new phone.
I was afraid of that.
I checked the post you mentioned but it seems I'd have to buy tools and hardware more expensive than the phone itself, so I'd rather buy a new smartphone.
Thanks for the help!
Hey I'll spare the story but basically I've softbricked/bootlooped my S4 in a way I have many times and fixed easily, however now I can't. Basically I tried to launch a bad ROM; same one thats failed me multiple times, stupid to try again but I've fixed this exact problem with this ROM before many times by flashing back to stock with Odin. The problem is my family computer was recently reformatted so I lost Odin, Kies, Drivers, anything I was using before. I redownloaded all those things only now none of them are working properly... When I load up Odin like I always have with my phone in download mode of course, select the tar and run. Only now it recognized a device is connected and I get a COM:03 or whatever but when I hit run it basically goes nowhere and just says "all threads complete completed 0 failed 0" or sometimes "completed 0 failed 1" can someone tell me what these messages are trying to tell me? I though maybe it was cuz I hadn't installed Kies but Kies says my device isn't responding, which I was told could be cuz I have a custom bootloader and my phone needs be 100% for Kies to recognize it but I feel like it used to recognize it with the custom loader. Maybe not. I also tried updating the windows USB drivers but everything was up to date. My computer makes a noise when I plug my phone in and charges it but can't be viewed in windows file explorer. Maybe that's cuz I'm in download mode.
I don't understand why it isn't working but I think its my computer. It's software is the only variable thats changed, I'm doing everything exactly as I used to. I think one of the many components to make this work isn't lined up properly and I don't know what it could be at this point. And PLEASE no answers like "did you check the USB port?". . . yes of course I checked the USB port, yes I'm in download mode, yes my cable works, redownloaded every program in multiple firmware versions. those are the only answers I've been able to find on this topic and none of them get me anywhere.
Can someone tell me what is different on my computers end now? As I've said, I've done this successfully 100 times on my computer before doing exactly what I'm now it just isn't working after the harddrive reset so I assume something has to be wrong on the computers end.
I have a VZWJFLTE SCH-I5454 galaxy s4 and I'm trying to boot back to stock (4.4.2 NC5 found on galxys4root.com).
Hi everyone,
I have an SII GT- I9100 that I installed a custom ROM on a while back (probably 2 years ago). After a while it got badly bricked I don't remember what happened, and not only that
the charging port was also messed up so I couldn't connect it to my pc (pc wouldn't recognize it unless I held the cable in with force, but even that didn't work after some time).
It's been sitting on a shelf for about a year and I decided to buy a new charging port, replace it, unbrick it and give it to my mom.
I did replace it and I can connect it to my pc now but there's still issues. On my main windows 10 pc it gives me an error "USB device not recognized, the last USB device you connected to this computer malfunctioned, and Windows does not recognize it". (I've reinstalled usb drivers and troubleshooted with Kies).
I keep the phone in download mode while I am trying to connect it to my pc since I can't boot into anything (I have a yellow triangle and Samsung logo if I don't go into download mode).
On my laptop (win 7) I've managed to get windows to install all the drivers(even though it failed a couple times ?), I've also troubleshooted with Kies, still Kies can't connect to it.
I want to restore it to stock ROM but I haven't been successful. First Odin gave me "setup connection" error but then I rebooted the pc and it "worked".
Now it just says complete (write) operation failed.
I've tried 3 different Odin versions, nothing.
What bothers me is that Odin says "Added !" but everyone online to the people with similar issue says that they should reinstall drivers or talks about USB Debugging (which I can't turn on or off since it's bricked).
Sorry for the long post but what's the move here? Am I using a bad ROM ? I've tried one for the country I live in but not the country from which the phone is ( I don't know the country, might be Austria), could this be the issue ?
Thanks in advance!
Update, I may have found the right ROM, now it's stuck at boot.bin
EDIT: Found a youtube "solution" to that, then it got stuck at cache.img
EDIT: Getting Driver issues again, Unknown Device :/
Hello there,
I am in the throws of trying to root my S6 edge (want to play using Magisk etc), but something just never happens when I try to do this through Odin.
I have the phone connected, everything seems fine with the file I am trying to use as an image, but nothing happens on the phone end at all. I get Succeeded 0 / Failed 0 as a response in Odin.
I have the drivers from Samsung installed. I even installed Kies. And I think this is where the problem is. I don't think the phone is being recognised. I have debug mode over USB on, but I just think the phone isn't being found by Odin.
Do any of you have some tips for me?
slim6y said:
Hello there,
I am in the throws of trying to root my S6 edge (want to play using Magisk etc), but something just never happens when I try to do this through Odin.
I have the phone connected, everything seems fine with the file I am trying to use as an image, but nothing happens on the phone end at all. I get Succeeded 0 / Failed 0 as a response in Odin.
I have the drivers from Samsung installed. I even installed Kies. And I think this is where the problem is. I don't think the phone is being recognised. I have debug mode over USB on, but I just think the phone isn't being found by Odin.
Do any of you have some tips for me?
Click to expand...
Click to collapse
Please be sure that Kies is not running (even not in background) when you run Odin. It won't work then.
In the past I only installed Kies to get the Samsung drivers installed. Afterwards, I immediately uninstalled Kies in order to have no trouble with Odin, and anyway if I've Odin I've no personal need for Kies.
Oswald Boelcke said:
Please be sure that Kies is not running (even not in background) when you run Odin. It won't work then.
In the past I only installed Kies to get the Samsung drivers installed. Afterwards, I immediately uninstalled Kies in order to have no trouble with Odin, and anyway if I've Odin I've no personal need for Kies.
Click to expand...
Click to collapse
I didn't have Kies installed the first time, and nothing worked. But even with Kies, I still can not get the PC to recognise any device. It is frustrating, because as far as I can see I have done everything right.
No matter what I do, I can not get the S6 to appear in Odin at all.
Further to this, despite having the drivers installed from Samsung, freshly today, the USB fails to be recognised (this is the issue). So I need to work out how to overcome this. Any suggestions?
More precisely, in the Device Manager, under USB, the failed USB states: "Unknown USB device (Device Descriptor Request Failed)".
*Update*
I did a factory reset on the S6 and still, no good. The device doesn't want to connect to any port in any computer with any cable.