Develop Bugs

Help Please! Firmware Encountered an issue.

Hi, I was attempting to root my phone (T989 on telus), I had gotten into the download mode, and odin had the phone recognized, yellow color and it said added.
But when I tried to do the recovery.tar step in here (http://forum.xda-developers.com/showthread.php?t=1332103) Odin came up with a big red FAIL.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now the phone says,
Firmware upgrade encountered an issue. Please select recovery mode in kies and try again. I looked at other threads, reinstalled drivers, pulled battery, restarted phone, and tried to recover with kies (which wouldnt connect) and to no luck.
Please help, I just bought this phone a month ago, and my uncle had been tellign me about how good rooting is.
EDIT: Ok somehow I fixed the problem.
I reinstalled keys, switched a usb port, downloaded recovery.tar again, and then tried to do the step again.
This time it worked, phone is now working.

One thing with using odin is that you want to use a usb port that i connected directly to the mother board. Not sure how you figure that out if your not a geek besides trial and error. Glad you fixed it though Only use that usb port from now on!

I was originally using one of the ports at the back anyway, which should be connected straight to the motherboard, but just in case I switched to a port lower down. It was either that or reinstalling the usb drivers. Needless to say, I almost crapped myself and I think ill stop here until I can get a friend who knows what he is doing to do this for me lol

Trying to restore my bricked epic, but need help!

Following the steps in the sticky at http://forum.xda-developers.com/showthread.php?t=1052813, I can get Odin to recognize the phone in download mode, but I get the following after a couple of minutes in the Odin status window:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D700-EL30-8Gb-REL.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
(It paused here for a minute or two)
<ID:0/009> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/009> Removed!!
The last line would be me unplugging the phone after seeing the word FAIL!! on a red background.
Help would be greatly appreciated.

Try using a different usb port and/or usb cables.

Everything you need is here:
http://forum.xda-developers.com/showthread.php?t=1052813
Including the 100's of suggestions a search would get you to try a better cable like a Blackberry and other USB ports, and reloading the drivers.

I tried multiple cables (I have 3), multiple ports (all 6 on my PC) and multiple computers (3, each with at least 4 USB ports, some running XP, some running Windows 7)
Only a few specific combinations allow Odin to even recognize the phone successfully. However, it always fails at "SetupConnection", as seen in the log.
The sticky I linked to does not address this, nor did I find anything specific to my issue in searching.

SweetBearCub said:
I tried multiple cables (I have 3), multiple ports (all 6 on my PC) and multiple computers (3, each with at least 4 USB ports, some running XP, some running Windows 7)
Only a few specific combinations allow Odin to even recognize the phone successfully. However, it always fails at "SetupConnection", as seen in the log.
The sticky I linked to does not address this, nor did I find anything specific to my issue in searching.
Click to expand...
Click to collapse
If its failing at setup connection, its most likely a bad cable... I see you have tried multiple cables, but apparently none of them are heavy duty data transfer cables... get yourself a good cable and then try it....

I have seen people that thought tgey had 4 good cables. They went a bought a thick Blackberry cable and odin went right through, no problem.
Sent from my PantechP4100 using xda premium

As soon as I can, I'll be gettiing a blackberry cable to try it.

[Q] Sprint S3 seems to be unrootable

my phone seems to be unrootable. I have tried everything, but I always get a write fail message after hanging at "Setup Connection" in Odin for a few minutes. My phone is recognized by my computer, I am able to drag and drop files to it. When plugged into Odin I am able to see the COM message. My phone does seem to have a hard time connecting to Kies, I believe it only connected to the software once.
Any solutions anyone?

If you're using ODIN, then uninstall Kies. It interferes with ODIN.
Also try switching cables, USB ports, and computers if possible.

NeedHelpNow said:
my phone seems to be unrootable. I have tried everything, but I always get a write fail message after hanging at "Setup Connection" in Odin for a few minutes. My phone is recognized by my computer, I am able to drag and drop files to it. When plugged into Odin I am able to see the COM message. My phone does seem to have a hard time connecting to Kies, I believe it only connected to the software once.
Any solutions anyone?
Click to expand...
Click to collapse
You can check HERE for more info on how to accomplish what you want to do. You can also use the S3 TOOLKIT. Lastly when in doubt you can check out THIS thread. If all else fails there's always THIS method .

Tried your suggestions already
prboy1969 said:
You can check HERE for more info on how to accomplish what you want to do. You can also use the S3 TOOLKIT. Lastly when in doubt you can check out THIS thread. If all else fails there's always THIS method .
Click to expand...
Click to collapse
Yeah did everything you listed, except for the toolkit. One thing I am noticing when I have my phone in download mode and it is plugged into the computer it registers as MSM8960, which from my search on google seems to be a chipset.
Thanks for the reply CNexus and prboy1969

Im curios to know if you unistalled the drivers and installed them again.
Sent from my SPH-L710 using xda premium

http://forum.xda-developers.com/showthread.php?t=1963812

Have you tired throwing it out a 3rd floor window. I heard that works.
http://i1202.photobucket.com/albums/bb374/TexasEpic/ThePeoplesROM-KennyGlass123/daniel4653.png

NeedHelpNow said:
Yeah did everything you listed, except for the toolkit. One thing I am noticing when I have my phone in download mode and it is plugged into the computer it registers as MSM8960, which from my search on google seems to be a chipset.
Thanks for the reply CNexus and prboy1969
Click to expand...
Click to collapse
One thing I would check is your USB mode may be set to debug. Look for the S3 dialer codes and find the one that changes the USB mode and switch it to PDA (I believe). If its on modem/debug or whatever else it may be the cause.
*EDIT: I think this may be why it shows up a MSM8960. I just tested my sprint S3 in odin mode and it shows up as "Samsung Mobile USB CDC Composite Device"
I would also suggest running the connection troubleshooter in KIES which re-installs the drivers. In my experiences KIES does not cause a conflict with ODIN (I've had both installed with no issues during my time with the S2 and S3).
Finally, reboot both the phone & PC, and try again. If it still fails swap out your USB cable.

rocket321 said:
One thing I would check is your USB mode may be set to debug. Look for the S3 dialer codes and find the one that changes the USB mode and switch it to PDA (I believe). If its on modem/debug or whatever else it may be the cause.
*EDIT: I think this may be why it shows up a MSM8960. I just tested my sprint S3 in odin mode and it shows up as "Samsung Mobile USB CDC Composite Device"
I would also suggest running the connection troubleshooter in KIES which re-installs the drivers. In my experiences KIES does not cause a conflict with ODIN (I've had both installed with no issues during my time with the S2 and S3).
Finally, reboot both the phone & PC, and try again. If it still fails swap out your USB cable.
Click to expand...
Click to collapse
In the past on older phones when I used a desktop the front usb ports wouldn't work had to use the back usbs. Try a different port?
Sent from my blue galaxy

You're in download mode and you've flashed the custom recovery right? Do a Google search of "how to root sprint Galaxy s3 androidcentral" and obviously click the one that says androidcentral
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 01:36 AM ---------- Previous post was at 01:32 AM ----------
Here's a link instead -
http://forums.androidcentral.com/sp...e-updated-how-root-your-sprint-galaxy-s3.html
Sent from my SPH-L710 using xda app-developers app

Follow whatever guide your using for how to use Odin.
Ie: just put the md5 file where its says PDA..
Put your phone in download mode..
Pull battery.. Put back.. Hold vol.down home and power..
Then at prompt push vol.up.
Phone will show I'm download mode.
The file.I would push is twrp.
The 2.5.0.0 works well on most all I do.
Once you have your custom recovery to install
Zips your good to go..
Just push the recovery and reboot the phone back into
The recovery mode..you shouldnt get errors.. I would say
To make sure your using a newer version of Odin and if you've
Messed with drivers always reboot PC.!!
Volume up.. Home and power this time..
And Go to recovery and flash whatever rooted ROM you want.

I'm good on computer anatomy and the ones in the back are usually fast, they are directly on the mobo
Sent from my SPH-L710 using xda app-developers app

Team DevDigitel said:
Follow whatever guide your using for how to use Odin.
Ie: just put the md5 file where its says PDA..
Put your phone in download mode..
Pull battery.. Put back.. Hold vol.down home and power..
Then at prompt push vol.up.
Phone will show I'm download mode.
The file.I would push is twrp.
The 2.5.0.0 works well on most all I do.
Once you have your custom recovery to install
Zips your good to go..
Just push the recovery and reboot the phone back into
The recovery mode..you shouldnt get errors.. I would say
To make sure your using a newer version of Odin and if you've
Messed with drivers always reboot PC.!!
Volume up.. Home and power this time..
And Go to recovery and flash whatever rooted ROM you want.
Click to expand...
Click to collapse
I have done everything you listed. Here is a question for you. When your phone is in download mode and you plug it in to the computer, what does it register as under Device & printers. I stated this before, but when I plug my phone in, it comes up as MSM8960. I did the S3 dialer code thing and all looks good, the phone is set to PDA and Qualcomm USB Settings are set to MTP+ADB (Thanks rocket321 for your assistance on that.)

Have you tried this method. It never fails comes with video and everything
http://qbking77.com/how-to-root/root-samsung-galaxy-s-iii/
Transmitted with a portable device using Xparent Blue Tapatalk 2

Tried that
edfunkycold said:
Have you tried this method. It never fails comes with video and everything
http://qbking77.com/how-to-root/root-samsung-galaxy-s-iii/
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I tried that tutorial, as a matter a fact that was the first one I used. When I check what drivers are being installed I see "SAMSUNG Mobile USB CDC Composite Device" and "SAMSUNG Mobile USB Modem #3" the #3 I am guessing is the USB port for which I am connected to (This number changes with every port when my device is connected to the computer). Does anyone get the same exact messages when they plug in their phone and drivers began to install? Odin Message below:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CWM-Recovery-LTE-SGS3-v5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

What Operating System is on your Desktop / Laptop?
TEAM MiK
MikROMs Since 3/13/11

NeedHelpNow said:
I tried that tutorial, as a matter a fact that was the first one I used. When I check what drivers are being installed I see "SAMSUNG Mobile USB CDC Composite Device" and "SAMSUNG Mobile USB Modem #3" the #3 I am guessing is the USB port for which I am connected to (This number changes with every port when my device is connected to the computer). Does anyone get the same exact messages when they plug in their phone and drivers began to install? Odin Message below:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CWM-Recovery-LTE-SGS3-v5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
As everything seems to be going right up until the flash, I might suggest you try flashing a different file.
Try CF-Auto-Root from the 3rd post in this thread: http://forum.xda-developers.com/showthread.php?t=1963812
Make sure you unzip to the .tar.md5 file and try flashing that in the PDA slot in Odin.
If that works you will have stock recovery but rooted ROM. From there you can use Mobile Odin to flash a customer recovery assuming you would like to have CWM or TWRP.

Windows 7
prboy1969 said:
What Operating System is on your Desktop / Laptop?
TEAM MiK
MikROMs Since 3/13/11
Click to expand...
Click to collapse
Windows 7

NeedHelpNow said:
Windows 7
Click to expand...
Click to collapse
So the Samsung drivers do install when you connect the phone to the PC? If that step is OK then have you tried a different USB port and a different USB cable? When Odin fails it is almost always a problem with the USB cable.
I have this same phone and I followed the QBKing77 video with no issues. It worked flawlessly but in the past Odin issues ended up being the USB cable.

NeedHelpNow said:
Windows 7
Click to expand...
Click to collapse
Have you made sure that the drivers are installed as suggested above. Also I'm not sure if I mentioned this. But I've had similar weirdness from using a bad USB Cable.
TEAM MiK
MikROMs Since 3/13/11

Bricked i9195

I bricked my S4 mini i9195.
When I try to enter recovery or just normal boot, nothing appears on screen, but it can boot to download mode.
So at firtst, I tried Odin, but it always stops at
<ID:0/004> SetupConnection.. or
<ID:0/004> Initialzation..
I also tried heimdall, it coudn't rescue my phone too.
In my computer(OS is Windows), my device is shown as SAMSUNG Mobile USB CDC Composite Device.
So I think it's not a hard brick like QHSUSB_DLOAD.
Is there any solution for me?

try something else. like turning off anti virus, closing kies or other samsung apps from task manager, and running the odin as administrator, or changing the usb port.

And also changing the cable. Try to not use a front USB port if it's a PC. If it's a laptop then change the port as suggested.

S9+ U1 Flash Instant Odin Error

So, originally my phone was ATT or Tmobile (I forget now), I flashed to U1 and stayed there for quite awhile. Then some months back I flashed to a Sprint U version. OTAs and everything worked. But Sprints version is missing some stuff that I came to love on the unlocked version.
I'm trying to go back to the U1 US unlocked (which is XAA region), and my boot loader is v7, and so is the U1 firmware I'm trying to flash with patched odin. I have USB Debugging enabled, removed the lockscreen and any sorts of locks.
My Sprint version is G965USQS7CSJ7, and the Unlocked I'm trying to go to is G965U1UEU7CSK1. I go into download mode/flash mode or what ever as usual, connect phone with the latest Samsung USB drivers installed with patched odin already open, its detected as 0:[COM3] in a cyan/light blue. I add the:
BL_G965U1UEU7CSK1
AP_G965U1UEU7CSK1
CP_G965U1UEU7CSK1
CSC_OMC_OYM_G965U1UEU7CSK1,
and after they all finish doing their checks, I start it, and It instantly stops.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 6714 M
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Am I missing something?
Edit: I downloaded patched odin again, and the firmware. Still the same error.
Edit 2: I tried to reflash my current firmware as well. Same issue.
Edit 3: Reinstalled USB drivers and ADB. Still nothing.
Final Edit: Issue solved. It was an issue specific to Ryzen CPUs. Just do it via what ever Intel system you have.

ReapersDeath said:
So, originally my phone was ATT or Tmobile (I forget now), I flashed to U1 and stayed there for quite awhile. Then some months back I flashed to a Sprint U version. OTAs and everything worked. But Sprints version is missing some stuff that I came to love on the unlocked version.
I'm trying to go back to the U1 US unlocked (which is XAA region), and my boot loader is v7, and so is the U1 firmware I'm trying to flash with patched odin. I have USB Debugging enabled, removed the lockscreen and any sorts of locks.
My Sprint version is G965USQS7CSJ7, and the Unlocked I'm trying to go to is G965U1UEU7CSK1. I go into download mode/flash mode or what ever as usual, connect phone with the latest Samsung USB drivers installed with patched odin already open, its detected as 0:[COM3] in a cyan/light blue. I add the:
BL_G965U1UEU7CSK1
AP_G965U1UEU7CSK1
CP_G965U1UEU7CSK1
CSC_OMC_OYM_G965U1UEU7CSK1,
and after they all finish doing their checks, I start it, and It instantly stops.
Am I missing something?
Edit: I downloaded patched odin again, and the firmware. Still the same error.
Edit 2: I tried to reflash my current firmware as well. Same issue.
Edit 3: Reinstalled USB drivers and ADB. Still nothing.
Click to expand...
Click to collapse
If your stuck on setup connection on Odin some things to try assuming using windows
Use Odin 3.13.1 ( or modified Odin 3.13.1B )
If you have smart switch/Kies install, un-install it.
USB cable i'm assuming is a data cable.
USB port try plugging into USB 2 port.
Plug phone directly into PC not any hubs.
Use latest Samsung USB drivers.
Run Odin in administrator mode.
Boot into download mode then reboot back into download mode again.
Maybe turn off any anti-virus/firewall programs.
Maybe plug/unplug leads a few times
Try a different PC.
These are a few things to try ( and some you've already tried ) as failing at setup connection can be a common issue with some people and can vary with the PC.

spawnlives said:
If your stuck on setup connection on Odin some things to try assuming using windows
Use Odin 3.13.1 ( or modified Odin 3.13.1B )
If you have smart switch/Kies install, un-install it.
USB cable i'm assuming is a data cable.
USB port try plugging into USB 2 port.
Plug phone directly into PC not any hubs.
Use latest Samsung USB drivers.
Run Odin in administrator mode.
Boot into download mode then reboot back into download mode again.
Maybe turn off any anti-virus/firewall programs.
Maybe plug/unplug leads a few times
Try a different PC.
These are a few things to try ( and some you've already tried ) as failing at setup connection can be a common issue with some people and can vary with the PC.
Click to expand...
Click to collapse
Have unfortunately done all of those listed minus the different computer thing which I'm transferring files for now.. Also its Odin 3.13.1_3B. I looked around and there's a good chance its a current Ryzen CPU issue.
Edit: Did appear to be a Ryzen issue. It worked smoothly on an Intel laptop.

ReapersDeath said:
Have unfortunately done all of those listed minus the different computer thing which I'm transferring files for now.. Also its Odin 3.13.1_3B. I looked around and there's a good chance its a current Ryzen CPU issue.
Edit: Did appear to be a Ryzen issue. It worked smoothly on an Intel laptop.
Click to expand...
Click to collapse
Glad it worked. It maybe with certain types of PC's out there. No issues on my HP laptop.

Ran into issues flashing XAA software on odin. Same problem, constantly failed on a Ryzen PC, tried it on an intel laptop and voila, it worked flawlessly. Thanks Reapersdeath for posting this solution.